using native client technology (nacl or pnacl) as opposed to to writing everything in javascript

[ghost]

hey, was wondering if i could hear everyone's thought's on implementing the chrome app client that acts as the bridge to the bt swarm (speaks both protocol) using the native client technology (nacl and pnacl) this is huge considering we can have thread support and the prospect of the browser executing c and c++ source files as machine code.
doesn't the benefits outweigh the chrome app CSP hurdles ? or am i missing something ?

also (may be missing something here) wouldn't releasing the client through node-webkit be detrimental to the adoption rate as opposed to a packaged chrome app because for webtorrent protocol to work there is a need for a high adoption rate.

[WebRTCGame]

How would this work with a 100% browser based, client side, implementation? There are other clients that work off of a chrome/firefox plugin, but none currently (that I'm aware of) that work without it. I had assumed that this was the goal, zero plugins. Maybe I'm wrong. My intention with webtorrent is to eventually create a per site peer based cdn. The last thing I would want is requiring users to download a plugin just for that. Now if you mean something like how processing.org let's you write in the processing hybrid language with custom script tags that parse on load, that might be something.

[ghost]

@WebRTCGame bitch stop hijacking my thread and start ur own

as for ur idiotic rant there are no browser that allow socket udp or tcp to be open on webpages for tabs this is not the webmodel this is unlikely to change as that would be huge change from the current web architecture,so there is no such thing as "a no plugin solution" ( the datachannel implementation of the webtorrent protocol needs plugin to access the bt swarm) in short the point of this is to start a new class of web based peers and seeders and then gradually achieving the no plugin haven!!!

there was a lot of detail i left because i don't feel the need to explain the entire thing to someone who can't even bother to read the documentation,the architecture has been discussed in detail before a lot times. ur rant has nothing to do with my thread so piss off and make ur own thread to talk about how u want stuff.

[WebRTCGame]

No.

[iShift]

close issue

[feross]

@superseige Your tone and vitriol is not welcome here.