method name

[Michael Hall]

On Jun 23, 2012, at 1:26 PM, Alan Bateman wrote:

> On 23/06/2012 15:44, Michael Hall wrote:
>> Seems a little trivial but also odd enough to ask about.  I'm not trying for a gotcha or anything but I'm seeing
>> getPathForExecptionMessage()
>> 
>> and it seems like that should be getPathForExceptionMessage()
>> shouldn't it?
> Yes, it must have been renamed in error at some point. I would suggest submitting a bug and bring a patch to nio-dev to fix this (it's an internal method, not a public API so there isn't any reason for to fix it).

One thing on this. With these nio.2 API's going in a more extensible direction. Wouldn't it make sense to have some of these classes more accessible.
For example, it looks like the watch service api's follow a similar pattern of including a Runnable Poller class to handle the threaded concerns. These extend a inaccessible, non-public, internal AbstractPoller class. Getting the threaded part of the code right for performance and scalability concerns would be an important concern in attempting a 3rd party watch services implementation. I would and am imagining. Modeling the existing implementations as much as possible would be helpful?