I’ve been experimenting with WebRTC connecting to the streaming engine.
Every multi-party sample application I’ve looked at creates a websocket for publishing, and then a separate websocket for each peer. This would mean that an N party conference call would require N*N connections to the server just for signalling!
It certainly appears that once a websocket has been established for publishing, it cannot then be used to send “getOffer” for a different streamName.
Obviously I’d prefer to just have a single websocket per client – is that possible?