You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
socket.io-p2p and its companion socket.io-p2p-server are no longer in working condition - don't expect to be able to use this module other than on a local network
#70
I am working on debugging several issues with socket.io-p2p. I hopefully will have a working copy for use with simple-peer 9.. soon.
Main bugs are double signaling - You'll notice this when running the outdated chat example when the receiving peer will receive the message twice. This bug has far worse consequences - makes cross network p2p connections impossible with the modules current logic.
This is a really cool middleware for p2p and websocket interaction and I wish it had more use.
The text was updated successfully, but these errors were encountered:
twofingerrightclick
changed the title
socket.io-p2p is no longer in working condition
socket.io-p2p is no longer in working condition - don't expect to be able to use this module
Nov 10, 2020
twofingerrightclick
changed the title
socket.io-p2p is no longer in working condition - don't expect to be able to use this module
socket.io-p2p and its companion socket.io-p2p-server are no longer in working condition - don't expect to be able to use this module
Nov 11, 2020
twofingerrightclick
changed the title
socket.io-p2p and its companion socket.io-p2p-server are no longer in working condition - don't expect to be able to use this module
socket.io-p2p and its companion socket.io-p2p-server are no longer in working condition - don't expect to be able to use this module other than on a local network
Nov 11, 2020
I am working on debugging several issues with socket.io-p2p. I hopefully will have a working copy for use with simple-peer 9.. soon.
Main bugs are double signaling - You'll notice this when running the outdated chat example when the receiving peer will receive the message twice. This bug has far worse consequences - makes cross network p2p connections impossible with the modules current logic.
This is a really cool middleware for p2p and websocket interaction and I wish it had more use.
The text was updated successfully, but these errors were encountered: