Hi Jeanfrancois,
I am working on using Grizzly for our server application which uses SSLv3
and a custom binary application level protocol for client-server talk. My
server side implementation of Grizzly and the problems I am facing are
similar to the ones in the thread below ...
http://www.nabble.com/Asynchronous-Request-Processing-with-TCPIP-td18234121.html
However I have some doubts before I implement the solution recommended in
the thread ...
I am going to implement both Async reads and writes on the server side and
the problem with adopting the solution for this is that once I suspend
execution of a ProtocolChain using the SuspendableFilter a call to
ctx.setKeyRegistrationState(KeyRegistrationState.NONE) is made, correct me
if I am wrong but, as a result of this reads won't happen on the channel. Is
there a way out for this? I do not want reads to be waiting on writes
caused by the previous read. I want reads and writes to be independent of
each other.
Also, I see that in case of Async writes for SSL / TLS the final channel
write happens in TCPAsyncQueueWriter.doWrite() using
channel.write(byteBuffer) call. I am supplying a write pre processor to wrap
my bytes before sending them out but, the part to redo the broken handshakes
before sending every chunk of bytes out to the channel as in
SSLOutputWriter.flushChannel() will be missing in TCPAsyncQueueWriter.
Please advice on how to work around this problem without drifting away from
the framework code and classes. For now, I am thinking of implementing a new
SSLAsyncQueueWriter.
Any help would be very much appreciated.
Thanks & Regards,
Phani
--
View this message in context: http://www.nabble.com/SSL-ARP-tp18381476p18381476.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.