Sam Jacobson

I was contacted by @nathany regarding this issue. I can't add an open source license to go.fsevents because it's not mine; it's a fork of Steven Degutis' code. I made...

I've forked fsnotify, and put together a rough implementation. See https://github.com/samjacobson/fsnotify. This is based on my "EventStream" code, and is not perfectly matched to fsnotify semantics yet. At present the...

There are a couple of places where the FSEvents API is not particularly compatible with fsnotify. Firstly; if you monitor a directory with FSEvents then the monitor is recursive; there...

@nathany I should note that above, one of the reasons I suggested a separate FSEventStream per watch was to support a separate throttle for each watch (as supported by your...

If the duration was global to the watcher then there would be more flexibility in the implementation of the FSEvents interface, ie it could use either one FSEventStream or many....

Good point regarding fallback.

@howeyc FYI From the FSEvents help: _latency_ The number of seconds the service should wait after hearing about an event from the kernel before passing it along to the client...

@nathany yes, that's the behaviour of kFSEventStreamCreateFlagNoDefer. The advantage of using the trailing edge is that close events can be coalesced. If the event is delivered on the leading edge...

@nathany my understanding is that in the leading edge case; evt1 happens and is delivered; the latency timer is started evt2 happens and is not delivered (yet); if evt3 happens...

Me too.