the performance difference is incredibly better with NIO!

I’ve added a fourth method to the DirectoryWatcherListener, onChanges

onChanges fires once per cycle and returns all the changes in an struct, with array for change, add and deleted file. This is easier for consumers to process changes in batches, rather than a whole series of individua; updates for every file which has been added, changed or deleted.

It’s up to the user to decide which approach they want to use

I also fixed the optional nature of ListenerMethods, if they are empty they are skipped.

The stopping logic was also a bit funky, it now behaves as expected.

There is a verboseLogging option too, which with the default example listener logs out a very detailed picture of everything which is going on.

All event gateway java threads are now labelled “Eventgateway-ID”, id being the name

One thing I noticed, when deleting a task, it only calls stop, if it’s in the running state.

https://github.com/lucee/Lucee/blob/6.0/core/src/main/java/lucee/runtime/gateway/GatewayEngineImpl.java#L124

In my testing, I did managed to delete a task which kept running in the background. I think it maybe better to just call the stop method regardless of the state?

I discovered stopped event gateways are restarted on shutdown as the context gets reset

i was exited when this was added to java, but then i have find out they do a lot of polling in the back (at least on Macos) as well with no control given.