Socket write scheduling woes

[ptr...@gmail.com]

Hi,

I'm working on an app with fairly intensive graphics and somewhat significant CPU use (around 20%), sending a few kb of OSC data every frame via a 'dgram' socket. It mostly works ok, but it seems that sometimes (at times predictably related to other significant JS processing happening, other times without such clear cause) it doesn't send any data for some time, eventually sending the accumulated packets in a spike. Depending on the circumstances, this accumulation might last a few seconds or several minutes (I'm pretty sure I've reached a configuration where the latter doesn't happen any more).

I'm still running on nw 0.6.3 here. I might try the later builds if it's likely to help, but since this work is going to be live in an exhibition soon I'm trying to keep such variables steady.

I wonder what my best approach is? I can't send the data from a WebWorker because of lack of Node support. It might be best to spawn a separate window and postMessage to it with the control data?

Cheers,

Peter