PeerJS — True peer-to-peer data in the browser
1–10 of 28 posts
Re: PeerJS — True peer-to-peer data in the browser
#2This looks like a really nice abstraction of the API. Will have to have a play with it over the weekend and see what ideas I come up with....
You can play with their chat demo here: http://cdn.peerjs.com/demo/chat.html
(Google Chrome 26.0.1403.0 or above is required)
Re: PeerJS — True peer-to-peer data in the browser
#3Any reason not to offer support for the video side of things? A lot of the issues in terms of client IDs and whatnot are the same. It would be nice to have a single library that can establish a connection and then send either video ir data or both...
Re: PeerJS — True peer-to-peer data in the browser
#4This looks like a really nice abstraction of the API. Will have to have a play with it over the weekend and see what ideas I come up with.... You can play with their chat demo here: http://cdn.peerjs.com/demo/chat.html (Google Chrome 26.0.1403.0 or above is required)
[deleted]
Re: PeerJS — True peer-to-peer data in the browser
#5Is a torrent client for iOS finally possible with that? One that runs in the browser and will piss off apple.
Re: PeerJS — True peer-to-peer data in the browser
#6Is a torrent client for iOS finally possible with that? One that runs in the browser and will piss off apple.
Potentially, but their Safari browsers don't support webRTC yet. There's also nothing you could do with the files once you had them, other than images.
I'd personally like to see them implement proper SVG support before they do too.
Re: PeerJS — True peer-to-peer data in the browser
#7> Note that no peer-to-peer data goes through the server; The server acts only to broker connections.
Q1. Does this support connecting to a peer behind a NAT device?
Q2. Does this support connecting two peers each behind its own NAT?
Because a vast majority of real world cases will fall into either of these two categories.
Re: PeerJS — True peer-to-peer data in the browser
#8Any reason not to offer support for the video side of things? A lot of the issues in terms of client IDs and whatnot are the same. It would be nice to have a single library that can establish a connection and then send either video ir data or both...
Is it totally possible to do both with the same library.Problem is: You need that?
I mean, video rendering kills the performance of your browser I guess is better just to show the possibility of data transferring and then you build it by using the desired specs. Many ongoing video demos are avaliable too :)
Those guys are also in the same ship with the browser P2P using WebRTC.
Re: PeerJS — True peer-to-peer data in the browser
#9> Note that no peer-to-peer data goes through the server; The server acts only to broker connections. Q1. Does this support connecting to a peer behind a NAT device? Q2. Does this support connecting two peers each behind its own NAT? Because a vast majority of real world cases will fall into either of these two categories.
Handles NAT traversals
Re: PeerJS — True peer-to-peer data in the browser
#10> Note that no peer-to-peer data goes through the server; The server acts only to broker connections. Q1. Does this support connecting to a peer behind a NAT device? Q2. Does this support connecting two peers each behind its own NAT? Because a vast majority of real world cases will fall into either of these two categories.
Handles NAT traversals
Any details?