Unfortunately WebSockets are limited to having a Server-Client paradigm.
So you must have something listening for the Websocket calls, and something which serves.
You could technically have an Assignment Client running on the Web Socket Server. Its job would be receives the socket calls and translates them into events for the client
The ICE / STUN does give the gateway address, but you have to fill in the blanks for the ports used.
This way, and request done would be done of the ws://place But the documentation for Assignment Clients is a tad bit spotty, so I have no idea where we may find examples or if there are any available… Needs more testing.
However there may be another method, but I am unsure if the QTBrowser supports it:
I’ve been theoretically mind storming a possible scenario where two WebRTC
clients are communicating with each other after an initial match up with a handshake server,
but WebRTC has not been tested with High Fidelity. It would allow for P2P connections.
However I haven’t put the effort yet into investigating if it actually works at all
It has not been tested yet. This means I do not have any examples available
Sorry that couldn’t be much help for now, Havent been doing enough actual experimentation in this part (only by mentally).