TypeError: Not enough arguments to mozRTCPeerConnection.createOffer. @ http://www.peer-server.com/shared/lib/peer.min.js:1
PeerServer: A Server in a Browser with WebRTC
11–20 of 27 posts
Re: PeerServer: A Server in a Browser with WebRTC
#12Won't connect for me (Fx 25, Linux). Blank white screen and this in the console: TypeError: Not enough arguments to mozRTCPeerConnection.createOffer. @ http://www.peer-server.com/shared/lib/peer.min.js:1
Re: PeerServer: A Server in a Browser with WebRTC
#13Nice! Why not chrome, exactly?
Last I checked Chrome's DataChannels implementation was flakey and missing support for several attributes
Re: PeerServer: A Server in a Browser with WebRTC
#14Quite interesting idea. On this we could have a distributed web server that scales as new ppl load the (site??). I can see this hurting akamai. People now have 10Mbps-20Mpbs up on DSL and cable; even before widespread FTOH this could become potent. It would also simplify a Tor alternative implementation, would'nt it?
Re: PeerServer: A Server in a Browser with WebRTC
#15Re: PeerServer: A Server in a Browser with WebRTC
#16Using profanity for needless shock value is not an effective way to get people to click your link.
Re: PeerServer: A Server in a Browser with WebRTC
#17Quite interesting idea. On this we could have a distributed web server that scales as new ppl load the (site??). I can see this hurting akamai. People now have 10Mbps-20Mpbs up on DSL and cable; even before widespread FTOH this could become potent. It would also simplify a Tor alternative implementation, would'nt it?
> People now have 10Mbps-20Mpbs up on DSL and cable; Are you talking about the bay area? I have never seen such an connection in a private home. (central and southern europe)
Re: PeerServer: A Server in a Browser with WebRTC
#18Re: PeerServer: A Server in a Browser with WebRTC
#19We are planning to open-source the code and create a brief video showing off its abilities this weekend, as well as fix some of the issues you may be having in more recent versions of Firefox. The WebRTC DataChannel spec has been changing, so it works in FF 22 (beta at the time we developed it) but breaks for some later versions where the API changed. It'll be fixed over the weekend for FF and the latest Chrome -- sorry for the issues some are having now.
Thanks for the great comments and enthusiasm!
Re: PeerServer: A Server in a Browser with WebRTC
#20"[22:21:01.082] TypeError: Not enough arguments to mozRTCPeerConnection.createOffer. @ http://www.peer-server.com/shared/lib/peer.min.js:1"