Hi Igor,
> 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?
It should have getConnection(), which is abstraction which represents
current connection.
> - no key == no ThreadAttachment == no SSLEngine for SSL. Is there a
> different way to get hold of the SSLEngine?
Yes :)
You can store everything using Connections and Attributes.
SSLResourcesAccessor.getInstance().getSSLEngine(connection);
> - no key == no way to cancel it
Hmm, that's true. We'll need to think about good way to do that. (can
you pls. file an issue)?
> - support for connection deregistration which was added to 1.9.x
> seems to be missing (SelectionKeyAttachment.DEREGISTERED)
Can you pls. elaborate? :)
> - 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.
Probably this was added after forking http 2.0 module.
> 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 :)
As for http module - not. framework module - yes.
WBR,
Alexey.
>
> /i
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>