Send rate is strange about peerjs-server

[ericz]

This seems to be the result of two issues.

The exception is due to Chrome's lack of support for binary data. You can
work around this by setting the serialization option in peerjs to none and
just sending strings.

The timing issues are a big stranger. They should work fine with SCTP data
channels... what version of Chrome are you using?

On Sat, Oct 26, 2013 at 8:34 PM, Eduardo Dias da Costa <
[email protected]> wrote:

First, thanks for the awesome tool! RTC can't be more easy :)

I have an application with an 'OnUpdate' callback wich sends data using
'connection.send(Time.elapsed)' each 0.1 seconds (~100ms).
In the receiving peer I put a 'console.log()' in the
'connection.on("data",...)' to check the data arriving.
For a bit of time it receives the string data correctly "1.1,1.2,1.3,..."
after sometime it starts receiving "1.3,2.3,3.3,4.3,..." (one 'data' event
per second). Eventually chrome catches this excetion too:

[image: image]https://f.cloud.github.com/assets/5433382/1414879/4e68b094-3eb8-11e3-8799-277e9ec2dbc7.png

The line error is here:

[image: image]https://f.cloud.github.com/assets/5433382/1414881/81e99ece-3eb8-11e3-8523-0239c0bcdea1.png

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/25
.

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

[eduardo-costa]

I edited the issue above.

The test was made with 2 Chrome tabs in the same window.
The loop in the unfocused tab will run in a rate smaller than 100ms.
Created the 2 test tabs in different windows and the loop was correct on both.

This avoided the slow send rate and the strange exception.
I think you can send an Uint8Array in it though!

Thanks!