-
Notifications
You must be signed in to change notification settings - Fork 24
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
feat: Allow reusing call instance [WIP] #1039
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we could add an unwatch
method that unregisters coordinator WS event listeners. It could be useful if a customer doesn't care about a call instance anymore, and then unwatch
should make it possible to GC the call instance.
I don't think our Coordinator API has such an API. We can handle this in the client, but the backend will still send events for unwatched calls. |
Yes, I meant handling client-side. I also didn't see backend support for this. |
Implemented with: #1433 |
Overview
Allows a
call
instance to be reused for multiple.join() -> .leave() -> .join()
cycles.Based on #1011 - I'll update the base once #1011 is tested and merged.