Le 12/18/12 3:41 PM, Hiller, Dean a écrit : > A bit late back to this thread but +1 from my side since as a user I > expected at least one nio library would have taken the approach that > parsing(decoding/encoding) should be a separate library from actual nio > frameworks. Instead it appears every library embedded/wired their parser > to be too coupled with the framework :(. > > The same goes for SSL as well ;). We wrote a SSL implementation that is > very easy to wire into an nio framework(open source) but it knows nothing > of the nio framework that uses it. (one we wrote about 7/8 years ago on > sourceforge before we knew about mina/netty). We did end up having to add > "Object passthrough" as a parameter in the api so the user can pass > through some information which is necessary sometimes, but it still didn't > need to be tightly coupled.
Interesting. Is it based on SSLEngine ? -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
