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

Allow for or extend checking connectedness of the provider #49

Open
lukashaertel opened this issue May 22, 2023 · 1 comment
Open

Allow for or extend checking connectedness of the provider #49

lukashaertel opened this issue May 22, 2023 · 1 comment
Assignees

Comments

@lukashaertel
Copy link

Is your feature request related to a problem? Please describe.
I want to properly check the connectedness status of the provider, I am unsure if the connected flag of the WebrtcProvider is properly representative of this status, as it is true if the room is created, but not if any networking has been done.

Describe the solution you'd like
One of the following come to mind:

  • The connection being properly represented as a flag so I can check it with e.g. promise.until from lib0
  • Connection events to resolve new promises
  • An async function in the provider connectedAsync that resolves if connected at call time or when the connection is established

Describe alternatives you've considered
Checking the connected flag, but as stated earlier, I am not sure if this is fully representative of what I would expect.

Additional context
I am not certain if a connection status can generally be determined in this configuration and if I am asking for a feature that cannot be implemented.

@lukashaertel
Copy link
Author

I think the core issue is the I am having problems when I want to dynamically create and destroy providers but run into issues that a room is already in use because I cannot properly determine when all the room and connection management is completed.

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

No branches or pull requests

2 participants