-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
No error event when connecting to non existent peers #566
Comments
we use setTimeout to hangup an outgoing call after X seconds. |
I'm doing the same but it seems highly suboptimal to have the client wait 5 seconds or so, when the server could respond with an error right away. |
I looked into the server code and it seems the server is waiting for the potential client to connect/reconnect before timing out the request. Wouldn't it be better to detect that the client with given ID has not existed for a long time? |
You're right. |
Implemented in server peers/peerjs-server#139 |
Thanks, that should be very helpful! |
This does not print anything:
Is there any way to distinguish failed connections, other than waiting for a timeout?
The text was updated successfully, but these errors were encountered: