Every connection to a WebSocket++ server will get its own unique connection_hdl
. This will happen if you open two WebSocket's from one application or the same application in multiple tabs/windows/computers.
Associating a given connection with a user is a pretty broad question. In short, like with non-websocket methods, you'll need to send along a username/password or session token to the server for each connection. If you want a single sign-on like effect between different tabs/windows you can use the browser's persistent client side storage (cookies, local storage, etc) to store those session tokens.