Skip to content
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

Change room name on an existing rtc-quickconnect instance #88

Open
IamCarbonMan opened this issue Aug 10, 2017 · 3 comments
Open

Change room name on an existing rtc-quickconnect instance #88

IamCarbonMan opened this issue Aug 10, 2017 · 3 comments

Comments

@IamCarbonMan
Copy link

Currently to allow a user to join a different room or channel, I have to create a completely new instance of rtc-quickconnect using the new room name. Is there any way around this?

@silviapfeiffer
Copy link
Member

What do you mean? Since every new room requires a whole RTCPeerConnection, of course you need to instantiate another rtc-quickconnect connection. What's your problem with that?

@IamCarbonMan
Copy link
Author

Having looked at the code, it's clear that it would be possible to do. In fact I was even considering writing it myself and contributing such a thing. But since it's clear that the project maintainers think I'm an idiot for even asking, nevermind.

Sent from my Google Nexus 5X using FastHub

@silviapfeiffer
Copy link
Member

silviapfeiffer commented Aug 27, 2017

Hi @IamCarbonMan - it wasn't meant to be insulting, but asking for clarification, because I was confused what you meant and whether it's even possible. If you think it's possible, you should absolutely try it! If it makes an app use less resources, then it's totally worth it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants