This doesn't make sense for JSS. It would make sense if JSS provided a subclass of java.net.SocketImpl that could be plugged into a generic java.net.Socket. But it doesn't work that way. JSS provides its own subclass of java.net.Socket. We don't even override java.net.SocketImpl, we just ignore the one we inherit from java.net.Socket.
We will provide a JSSE implementation, and that should make it easier to plug the JSS SSL socket implementation into generic apps. Patrick wrote: >Jamie, > >Would it make sense to you to have an implementation of >java.net.SocketImplFactory (called sometime like SSLSocketFactory) in JSS, >which would do all the SSLSocket and SSLServerSocket classes so? That way I >could slip JSS security under any application relatively painlessly by doing >a simple setSocketImplFactory(SSLSocketFactory). > >What do you say? > >
