Hi,
Sorry I didn't quite catch this mail and you probably moved on.
Anyway, I'm still not happy with the SSL-implementation I've made.
The main reason the SSL-implementation is weak is because I'm not personally using Naga with SSL. In fact, I think if you're starting to play around with SSL then Naga isn't your best choice. There are other, more framework-ey libraries for that.
Naga is really just the basic foundation code you need whenever you're writing standard asynchronous sockets, especially server-side sockets.
My own experience with socket security usually leads me *away* from SSL, and towards proprietary solutions. There are advantages and disadvantages with either approach. If you roll your own security, it's easy to make mistakes as well.
In the cases I would want to use SSL for a simple project, I'd probably use normal sockets + threads on java (despite the headaches that entails).
There are some SSLSocketChannel "implementations" available, but they provide a leaky abstraction. The best I could do without writing a few SSL projects with naga is the very alpha-state implementation available.
I don't recommend using it. If you need SSL and you can't implement it on top of Naga, Naga might not be your ideal choice anyway.
/C