A filesystem-change event becomes ready if there's a change between the time that you create the event and the time that you poll it. After the change event becomes ready, it stays ready, so you'd need create a new filesystem-change event to watch for further changes.
With that interface, these questions of granularity don't apply, because your program is in charge of how often it creates and checks filesystem-change evts. Then again, it also means that the filesystem-change API doesn't tell you what has changed. At Thu, 12 Oct 2017 14:58:09 -0400, David Storrs wrote: > Suppose I'm watching a directory such that I will receive > filesystem-change-evts when things are added/deleted/renamed. Someone > drag-n-drops 4,000 files into the directory. How will the system > handle this? > > 1) Will I receive an event every time the OS starts copying the next > file, will it batch them up, or what? > > 2) If it batches them, what is the granularity? > > 3) How does this vary across OSes? > > -- > You received this message because you are subscribed to the Google Groups > "Racket Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to racket-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
