-
-
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
error event not triggered #626
Comments
@tiofabby Hi, tifabby. I came across the same problem.
|
Hello @begoat I am thinking about putting a Timeout to close these ghost connections never being opened.. but I would prefer peerjs to have these detected so I can trigger their closing automatically. Thanks |
Are there any error logs on console?
Wednesday, February 19, 2020, 17:56 +0800 from [email protected] <[email protected]>:
…Hello @begoat
Thanks for your feedback but I had that in place already and if I try to connect to a peer not being connected to the server, the peer.on('error', function(err) { ... }) is not being triggered neither.
I am thinking about putting a Timeout to close these ghost connections never being opened.. but I would prefer peerjs to have these detected so I can trigger their closing automatically.
Thanks
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub , or unsubscribe .
|
Hi @begoat |
Hello,
I am able to send data between two peers, using your peerjs-server (v0.2.9) without any issues and it works fine.
Only problem I am facing is that if one of the 2 peers is offline, the peer.connect() to such user (being offline) will never trigger the 'error' event even if we listen to it.
Is it on purpose or am I missing something?
Please note also that if peer is online at the beginning, I am then able to connect to it. Then if such peer gets OFFLINE suddenly, then in that case the 'error' event is correctly triggered!!
So the issue here is only when peer is offline since the beginning and we are never able to connect to it, then in that case, the 'error' event is never triggered.
Thank you
Fabrice
The text was updated successfully, but these errors were encountered: