The SSLEngine implementation that went into the current build was a
proof-of-concept prototype, and allows developers to play with the
APIs. While functional, this is not the the way it should be implemented.

This bug is to finish the SSLEngine to have it's own classes, and not
be a wrapper over the top of the existing SSLEngine.

If time allows, also rewrite the SSLSocket to use the new SSLEngine, otherwise
wait for dragon.

###@###.### 2003-08-21