Websocket client creates two threads per SSL client connection - intended or accidental?

[Barry Coughlan]

Each AsyncChannelWrapperSecure creates two threads, and
WsWebSocketContainer creates an AsyncChannelWrapperSecure for each secure
connection.

Is this behaviour intended or is this a bug?

I initially posted this as a bug because:
1. The behaviour is not mentioned in the Websocket How-To
2. The behaviour only happens with secure connections
3. It's very inefficient, especially considering the How-Tos emphasis on
not using the BIO connector.


Barry