- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Tue, 12 Jan 2016 17:36:04 +0000
- To: public-secondscreen@w3.org
tidoust has just created a new issue for https://github.com/w3c/presentation-api: == bufferedAmount property on PresentationConnection == Still looking at similarities with WebSockets and WebRTC data channels, I note that they both define a `bufferedAmount` property that returns the number of bytes of application data queued using `send()` but not yet transmitted to the network. This property is typically useful for a Web app to handle congestion issues and e.g. prioritize messages to transmit or otherwise postpone non essential transmissions. Should we have a similar mechanism? WebRTC goes a bit farther than WebSockets and also defines a `bufferedAmountLowThreshold` and a `bufferedamountlow` event. Please view or discuss this issue at https://github.com/w3c/presentation-api/issues/241 using your GitHub account
Received on Tuesday, 12 January 2016 17:36:06 UTC