[
https://issues.apache.org/jira/browse/HTTPCORE-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511755
]
Andrea Selva commented on HTTPCORE-48:
--------------------------------------
Thanks,
i've readed some chapters of the Java NIO book, and now i've a more clean
ideas about async io in java. I've tried to use a trivial executor, posting
(invoking execute) a Runnable subclass that wrap the two core handshake
invocations (this.sslEngine.beginHandshake(); doHandshake()) but this create a
break in ssl negotiatin during some unittest. So i've seen that SSLEngine give
a util method (getDelegatedTask()) to return a Runnable, so i've used it, but
this runnable is alway null. In your opinion the best way to follow is that of
getting a Runnable from getDelegatedTask() and then run it in an executor?
Andrea
> Make SSL IOSession decorator to use an Executor interface to execute all
> potentially blocking handshake tasks
> -------------------------------------------------------------------------------------------------------------
>
> Key: HTTPCORE-48
> URL: https://issues.apache.org/jira/browse/HTTPCORE-48
> Project: HttpComponents Core
> Issue Type: Improvement
> Components: HttpCore NIO
> Reporter: Oleg Kalnichevski
> Fix For: 4.0-beta1
>
>
> Presently the SSL IOSession decorator executes all potentially blocking
> handshake tasks on the I/O thread. Use an Executor interface from
> java.util.concurrent to make possible the execution of handshake tasks using
> worker threads, thus making the I/O thread available for processing I/O
> events even if some SSL connections are blocked pending completion of a
> handshake task.
> Oleg
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
