8 ms·
PeerJS — True peer-to-peer data in the browser
- samwillis 14y agoThis 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 http://cdn.peerjs.com/demo/chat.html (Google Chrome 26.0.1403.0 or above is required)
- deleted 14y ago[deleted]
- silverlight 14y agoAny 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...
- churreiro 14y agoIs 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 :) http://webp2p.org/ http://webp2p.org/ Those guys are also in the same ship with the browser P2P using WebRTC.
- jonpaul 14y agoCheck out Holla.js for Video/Audio: https://github.com/wearefractal/holla https://github.com/wearefractal/holla
- ericz 14y agoIt's in the works!
- venomsnake 14y agoIs a torrent client for iOS finally possible with that? One that runs in the browser and will piss off apple.
- nwh 14y agoPotentially, 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.
- jonknee 14y agoKind of hard when you can't store to the filesystem.
- venomsnake 14y agoDirect torrents no, but you can rename the pieces *.fll and download them and send them to registered app for that extension that combines them ... you will have problem with seeding though, but that is also something that can be solved with a little tweaking of the protocol. I think the hacker community has shown that they can scare you with their inventiveness when they work in (stupidly and unnecessarily in that case) constrained environment.
- huhtenberg 14y ago> 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.
- dalore 14y agoHandles NAT traversals
- huhtenberg 14y agoAny details?
- churreiro 14y agohttp://dev.w3.org/2011/webrtc/editor/webrtc.html#rtciceserver-type http://dev.w3.org/2011/webrtc/editor/webrtc.html#rtciceserve... Specifications here
- deleted 14y ago[deleted]
- churreiro 14y agoIt is NAT reversal, even there are still many issues to be solved with the ICE. WebRTC team is working fast in this aspect... BTW, consider that they are shipping first final version in march so NAT reversal is important. YEY!
- vr000m 14y agoIt uses SDP to exchange ICE candidates. At the moment the SDP tries to multiplex video/audio and SCTP (data channel).
- latitude 14y ago
- Hupo 14y agoLooks like a nice little library, and very relevant to my interests. My personal "dream scenario" is to have true multisource P2P video streaming in the browser with no extensions required - with WebRTC, this seems quite feasible as implementations mature.
- deleted 14y ago[deleted]