# single WebrtcTransport with multiple producers and consumers

**URL:** <https://mediasoup.discourse.group/t/single-webrtctransport-with-multiple-producers-and-consumers/4101>\
**Category:** mediasoup libraries\
**Created:** [April 13, 2022, 6:07pm UTC](https://mediasoup.discourse.group/t/single-webrtctransport-with-multiple-producers-and-consumers/4101 "2022-04-13T18:07:20Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![snnz](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/snnz/32/693_2.png) [@snnz](https://mediasoup.discourse.group/u/snnz)\
**Post date:** [April 13, 2022, 6:15pm UTC](https://mediasoup.discourse.group/t/single-webrtctransport-with-multiple-producers-and-consumers/4101/2 "2022-04-13T18:15:37Z")

</div>

Take a look at this topic: [What are the design limitations leading to separate send/receive transports on the client and can we lift them?](https://mediasoup.discourse.group/t/what-are-the-design-limitations-leading-to-separate-send-receive-transports-on-the-client-and-can-we-lift-them/996)

---

_[View the full topic](https://mediasoup.discourse.group/t/single-webrtctransport-with-multiple-producers-and-consumers/4101)._