Are data channels send/receive chunk size limits still present?

[Szymon Nowak]

Hi,

like in the topic: are data channels send/receive chunk size limits still present in the latest versions of Chrome and Firefox? If they are still there, have they somehow changed in the last year?

I'm thinking about ways to optimize file transfer speed in my app (sharedrop.io), but if I could send data in larger chunks that would be the simplest option.

Cheers,

Szymon

[Kaiduan Xie]

Assume SCTP data channel is used, it seems that the limitation is here,

http://code.google.com/p/webrtc/source/browse/trunk/talk/app/webrtc/datachannel.cc

static size_t kMaxQueuedReceivedDataBytes = 16 * 1024 * 1024;

static size_t kMaxQueuedSendDataBytes = 16 * 1024 * 1024; /Kaiduan

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Szymon Nowak]

Thanks! I really hoped they're gone... Does anybody have any info about QUIC protocol in WebRTC data channels?

[Justin Uberti]

FYI, those limits aren't the chunk limits - those are the maximum amount of buffered data, which will exist even after chunk limits are gone.

Follow https://code.google.com/p/webrtc/issues/detail?id=2276 for updates on relaxing the chunk limits.

No updates yet on QUIC for data channels.

[Wang Sheng]

I don't understand why the "send buffer" can be a problem webrtc in chrome .   Javascript is dynamice object ref language , if the object haven't been sent by underground webrtc, the  object won't be released by  Javascript executing environment .   RTCDataChannel.send should return promise object which will notify the send finished . 

Why datachannel always has such problem. 

在 2015年1月27日星期二 UTC+8上午9:58:33，Justin Uberti写道：