Re: [ppsp] FWI

Actually, given WebRTC in the browser, UDP is not needed that much.
PPSP can be run over WebRTC, just use larger bins (64KB or so). Except
for LEDBAT, maybe.
But you'll have to keep the tab open to seed, that's uncool.

On 7 March 2014 18:44, Johan Pouwelse <peer2peer@gmail.com> wrote:
> Hi All,
> A plug-in is required for Chrome.
>
> Only "Chrome Apps" have access to the UDP API it seems:
> http://developer.chrome.com/apps/app_network
> For Firefox, is this also "plug-in only"?
>   -j
>
> On 5 March 2014 12:30, Dave Cottlehuber <dch@skunkwerks.at> wrote:
>> Hey folks,
>>
>> I have been following these tickets/features with interest for a while;
>>
>> firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=952927
>> chrome: http://developer.chrome.com/apps/sockets_udp
>>
>> also, http://thenextweb.com/google/2013/06/27/google-adds-its-udp-replacement-quic-network-protocol-to-latest-chrome-build/ is intriguing. Keep an eye on it in https://groups.google.com/a/chromium.org/forum/#!forum/proto-quic
>>
>> A+
>> --
>> Dave Cottlehuber
>> Sent from my PDP11
>>
>> _______________________________________________
>> ppsp mailing list
>> ppsp@ietf.org
>> https://www.ietf.org/mailman/listinfo/ppsp
>
> _______________________________________________
> ppsp mailing list
> ppsp@ietf.org
> https://www.ietf.org/mailman/listinfo/ppsp

-- 
Victor

Re: [ppsp] FWI - raw UDP socket access in browsers