- From: François Daoust via GitHub <sysbot+gh@w3.org>
- Date: Fri, 12 Jun 2015 15:31:56 +0000
- To: public-secondscreen@w3.org
During the F2F, we wondered about how WebSockets and WebRTC handled
messages consisting of and empty string. I investigated and totally
agree with @mwatson2 that the algorithms described in both specs do
not treat empty strings in any special way, and thus empty strings
should be treated as any other string message, following the exact
same steps.
In other words, calling `send('')` should send an empty string over
the communication channel and trigger a `message` event on the
receiving side. This is exactly what happens in all WebSockets
implementations that I tested.
However, as reported by @avayvod during the F2F, Chrome and Firefox
silently drop empty string messages sent over a WebRTC data channel
for the time being. I believe that is a bug in the way they interpret
the specification and I submitted a test case for the WebRTC test
suite that specifically checks that point, see:
https://github.com/w3c/web-platform-tests/pull/1897
I do not think that we need to change anything in the Presentation API
for that.
--
GitHub Notif of comment by tidoust
See
https://github.com/w3c/presentation-api/issues/46#issuecomment-111528995
Received on Friday, 12 June 2015 15:31:59 UTC