Serialization should be async

[manvalls]

When large files are being prepared to be sent the execution of the serialization will block the javascript event loop, making the page unresponsive.

In addition, when using unreliable datachannels you're assuming your data may arrive unordered, thus if the user sends a 10kB file while a 50MB one is being prepared the 10kB one should be sent right away, at least when using unreliable datachannels.

I can think of two solutions to this problem:

1- Replace function calls with setTimeouts

function doSomething(data){
       if(data.length > 0xf) setTimeout(doSomethingElse,0,data);
}

2- Use web workers

Web workers are the way to go imo, as nowadays even phones have more than one core. And if a browser supports webrtc, it will already have support for web workers.

PS someone tell eric I made a sizeof function for javascript, he isn't answering my emails - nobody likes me :(

[michelle]

Ha, @ericz should be answering soon :P.

[ericz]

NO I DO LIKE YOU.. Sorry I'm quite busy with the job these days so I'm slow
on the emails.

On Tue, Dec 17, 2013 at 11:30 PM, Michelle Bu notifications@github.comwrote:

Ha, @ericz https://github.com/ericz should be answering soon :P.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/131#issuecomment-30822051
.

510-691-3951
http://ericzhang.com

[manvalls]

Ü happy manvalls is happy!!

Anyways, any thoughts about web workers?

I'm currently dropping socket.io in favour of peerjs @ chatiku.com, so you'll see me around here in a regular basis btw

[michelle]

+1, but definitely would need to benchmark it.