Hello.
Implementing Grizzly benchmark measurement, I've found out that
currently SSLReadFilter doesn't support chunked reading. If secured
chunk came, but it's not enough for SSLEngine to decode info - next
time, when second chunk will come - SSLReadFilter will not be able to
concatenate these chunks! As currently secured input buffer and secured
output buffer are associated with Thread, but not with SSLEngine
session. And if 1st and 2nd chunks will come in separate threads - error
will occur.
To avoid this problem I think we need to associate secured buffers with
SSLEngine's session, at least it makes sense, when there is some secured
data (input or output), which should be used with next time during
read/write operations. For WorkerThreadImpl - we can implement some
common attribute map interface: setAttribute(String name, Object obj),
getAttribute(String name) and remove members: inputBB, outputBB, sslEngine.
What do you think?
WBR,
Alexey.