WebSockets are not intended as clear "stream" channels over which other existing protocols can be implemented.

WebSockets are designed to allow messages to be sent between a client and server, where an event is raised each time a message is received.

Hence a WebSocket client cannot simply connect to an existing TCP server - that server also has to speak the WebSocket protocol.

You could of course write a WebSocket-based server that does nothing but act as a proxy to existing network services.

WebSockets are not intended as clear TCP channels over which other existing protocols can be implemented.

WebSockets are designed to allow messages to be sent between a client and server, where an event is raised each time a message is received.

Hence a WebSocket client cannot simply connect to an existing TCP server - that server also has to speak the WebSocket protocol.

You could of course write a WebSocket-based server that does nothing but act as a proxy to existing network services.

WebSockets are not intended as clear "stream" channels over which other existing protocols can be implemented.

WebSockets are designed to allow messages to be sent between a client and server, where an event is raised each time a message is received.

Hence a WebSocket client cannot simply connect to an existing TCP server - that server also has to speak the WebSocket protocol.

WebSockets are not intended as clear "stream" channels over which other existing protocols can be implemented.

WebSockets are designed to allow messages to be sent between a client and server, where an event is raised each time a message is received.

Hence a WebSocket client cannot simply connect to an existing TCP server - that server also has to speak the WebSocket protocol.

You could of course write a WebSocket-based server that does nothing but act as a proxy to existing network services.