-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not using pair key in pipeToRouter()
#738
Comments
Please let's not open issues in GH for asking questions or having discussions.
Yes |
Yeah, sorry for that, I first was writting a bug report since only saw the first |
Code got a bit complex to avoid having global state, but not that much. |
Logic is fine, and I really like the aproach, very smart :-) It's more about code structure, that Promise with Promise.then() inside... ugh :-/ |
At
mediasoup/node/src/Router.ts
Line 725 in ec186c5
pipeToRouter()
is using only destination Router ID as key of the pair of Router instances, as it was discussed in #697. Later onmediasoup/node/src/Router.ts
Lines 810 to 813 in ec186c5
mapRouterPairPipeTransportPairPromise
withrouter.id
and ataddPipeTransportPair()
withthis.id
, so not using pair key at all but just storing them twice (equally acceptable) and removing it later on bothmediasoup/node/src/Router.ts
Lines 774 to 786 in ec186c5
mediasoup/node/src/Router.ts
Lines 949 to 966 in ec186c5
[this.id, router.id].sort().join(',')
part, isn't it? Or am I missing something? Are we storing the pair in local pairs and also in remote Router ones instead of having a common list with unique IDs? Is it just not using a global list the only reason of doing it that way?The text was updated successfully, but these errors were encountered: