A DESCRIPTION OF THE REQUEST :
On operating systems which support watching an entire directory tree, hitting the hard-coded limit of 512 events before AbstractWatchKey runs out of space is way too easy to hit.

In the first place, I'm not even sure why you have to impose a limit. If you're going to impose a limit, it should at least be configurable.


JUSTIFICATION :
On Windows, it is impossible to watch every folder in a hierarchy, because registering a WatchService on a directory currently prevents the user from deleting directory.

The workaround for this is to install the watcher to watch the entire directory tree. The problem is, when a large number of files are copied into the directory, the watch service can't keep up with the updates. The limit of 512 is hit immediately.

The presumed "correct response" to an OVERFLOW event is to reset the watch status. My experience is that when you do this, the updates quickly flood in again and you get another OVERFLOW event.

This effectively makes the API unusable on Windows, as watching the entire tree is impossible due to guaranteed overflow and watching individual directories is impossible due to the user not being allowed to delete the directory normally.