Hello,
Jeanfrancois Arcand wrote:
> In fact, I think SSLImplementation and
>> SSLConfig do more or less the same thing , to the point that they
>> conflict with each other. Perhaps making SSLConfig implement an
>> interface just made of "SSLContext createSSLContext()" and let people
>> configure the relevant class would be enough (and removing/deprecating
>> SSLImplementation). This would certainly avoid some of the problems
>> I'm describing below.
>
> Agree. The history of why we have both is with v2, we were supporting
> blocking I/O and non blocking. Non blocking needed SSLConfig, blocking
> I/O not. Can you file an issue in Grizzly under:
>
> https://grizzly.dev.java.net/servlets/ProjectIssues
>
> Note that there is some work already related to SSLConfig
>
> https://grizzly.dev.java.net/issues/show_bug.cgi?id=494
I've just filed this issue (based on my original message, slightly
rephrased):
https://grizzly.dev.java.net/issues/show_bug.cgi?id=508
Best wishes,
Bruno.