nill
Is there any limit on number of sessions a client can create?. Why is one session recommended for all tracks when we can simplify and have separate session for each track?
Each session requires you to establish a PeerConnection. Technically you could create a new PeerConnection for each track. But I would advise against that as each PeerConnection creates an overhead on both ends.
If you do put each track into a new PeerConnection you can compare it to establishing a new TLS connection with the server for every single HTTPS request. Technically you can do that, but it is most likely not a very solution in the end.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.