An abstraction layer for webRTC. Aim is to simplify the HTML5 web standard webRTC in a similar manner to socket.io w/ websockets. Highly experimental technology
I'm working with the Named-Data-Networking team and the Dean of Technology and Innovation at UCLA and currently am the author of a library called "worker.io" which uses SharedWorkers for shared-state across tabs, per domain.
Our dilemma is that we need shared-state across of different domains in a secure way WITHOUT a webserver, so I found webRTC.io.
Is there any way to remove a server entirely from the stack using webRTC.io (or any other workaround)?
Cheers,
Cody
ps. feel free to close this issue and email me at otocarlson@gmail.com
Hi,
I don't know how to contact the authors.
I'm working with the Named-Data-Networking team and the Dean of Technology and Innovation at UCLA and currently am the author of a library called "worker.io" which uses SharedWorkers for shared-state across tabs, per domain.
Our dilemma is that we need shared-state across of different domains in a secure way WITHOUT a webserver, so I found webRTC.io.
Is there any way to remove a server entirely from the stack using webRTC.io (or any other workaround)?
Cheers,
Cody
ps. feel free to close this issue and email me at otocarlson@gmail.com