No that is not what i meant.
I'm more use to create an objects that acts as a Server end points for the Websocket Server. So you would then make a connection to:
And so on. In side the Visual C++ I have something along these linesWebsocketServer server; server.registerService(new SomeEndPointClass1, "endpoint1"); server.registerService(new SomeEndPointClass2, "endpoint2"); server.registerService(new SomeEndPointClass3, "endpoint3");
Then the individual class/object would take handle the communication and the Websocketserver is just there to route the incoming packets to the Endpoint.