(ml5717) Added peer.js npm install
Showing
- .pre-commit-config.yaml 2 additions, 2 deletions.pre-commit-config.yaml
- README.md 35 additions, 1 deletionREADME.md
- package-lock.json 5023 additions, 0 deletionspackage-lock.json
- package.json 14 additions, 7 deletionspackage.json
- server.js 29 additions, 0 deletionsserver.js
- src/app.js 22 additions, 0 deletionssrc/app.js
- src/y-webrtc/LICENSE 21 additions, 0 deletionssrc/y-webrtc/LICENSE
- src/y-webrtc/index.js 57 additions, 0 deletionssrc/y-webrtc/index.js
Loading
-
@ml5717 Weren't we going to do it on the server first? :(
EDIT: Ah, nm. That's what
PeerServer
is.Edited by Nayeem Rahman -
@mnr17 You are partially correct. This code right now skips the “all messages through the server” phase - but purely as it doesn’t implement any actual data passing functionality of any kind yet and I wanted to see if this library can work (i.e. compile and give users a unique ID). My plan is to still add some p2p functionality using a central signalling server today, so we have something to work off when we try to add purely centralised communication (there is a XMPP extension for y-js).
Please register or sign in to comment