# WebSocket reuse

**URL:** https://community.wowza.com/t/websocket-reuse/91930
**Category:** Wowza Streaming Engine
**Tags:** webrtc
**Created:** [September 16, 2020, 12:23pm UTC](https://community.wowza.com/t/websocket-reuse/91930 "2020-09-16T12:23:30Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![tom\_mr](https://avatars.discourse-cdn.com/v4/letter/t/6a8cbe/32.png) [@tom\_mr](https://community.wowza.com/u/tom_mr)
#### Post date: [September 16, 2020, 12:23pm UTC](https://community.wowza.com/t/websocket-reuse/91930/1 "2020-09-16T12:23:30Z")

</div>

Hello,

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?

Thanks

---

<div class="post-metadata">

### Author: ![Daniel\_Rossi](https://avatars.discourse-cdn.com/v4/letter/d/e95f7d/32.png) [@Daniel\_Rossi](https://community.wowza.com/u/Daniel_Rossi)
#### Post date: [September 22, 2020, 6:03am UTC](https://community.wowza.com/t/websocket-reuse/91930/2 "2020-09-22T06:03:45Z")

</div>

This is what I have had to do to signal new published streams for subscribing

---

<div class="post-metadata">

### Author: ![Remy\_G](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/remy_g/32/487_2.png) [@Remy\_G](https://community.wowza.com/u/Remy_G)
#### Post date: [September 25, 2020, 5:58pm UTC](https://community.wowza.com/t/websocket-reuse/91930/3 "2020-09-25T17:58:36Z")

</div>

This is not possible. Also, Wowza is not really suitable for conferencing solutions, more suitable for one-few to many.

---

<div class="post-metadata">

### Author: ![tom\_mr](https://avatars.discourse-cdn.com/v4/letter/t/6a8cbe/32.png) [@tom\_mr](https://community.wowza.com/u/tom_mr)
#### Post date: [September 25, 2020, 6:13pm UTC](https://community.wowza.com/t/websocket-reuse/91930/4 "2020-09-25T18:13:28Z")

</div>

Thanks Remy. “Conference” call is probably stretching the terminology a little – we’re not talking about enormous numbers of people, but greater than two.

Did seem odd that it required a new, socket, for, every, single, pair, of, clients, but if that’s the cost of doing business then we’ll have to do it until we can upgrade to a less eccentric solution.

---

<div class="post-metadata">

### Author: ![Remy\_G](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/remy_g/32/487_2.png) [@Remy\_G](https://community.wowza.com/u/Remy_G)
#### Post date: [September 25, 2020, 6:24pm UTC](https://community.wowza.com/t/websocket-reuse/91930/5 "2020-09-25T18:24:50Z")

</div>

It’s very quick and disconnected after setting up the connection. Usually setting up the connection and getting the info will take a few secs and then it’s free’d up again.
