Hi guys,
I had a brief look at integrating grizzly-sendfile with grizzly 2.0-m3
(via an AsyncFilter) and noticed these issues:
- ProcessorTask doesn't have getSelectionKey() method. Is there a way
to get hold of the selection key?
- no key == no ThreadAttachment == no SSLEngine for SSL. Is there a
different way to get hold of the SSLEngine?
- no key == no way to cancel it
- support for connection deregistration which was added to 1.9.x seems
to be missing (SelectionKeyAttachment.DEREGISTERED)
- ProcessorTask#setForceKeepAlive available in 1.9.x is missing in
2.0. This api might not be necessary any more if the connection
deregistration was implemented properly.
Other than that everything seems to be the same as 1.9.x (when it
comes to source compatibility of the api), which is a bit surprising.
I expected many more api changes. Are more breaking changes coming? I
kind of hope they are :)
/i