[whatwg] Thread to run Web Socket feedback from the protocol ?
Fumitoshi Ukai (鵜飼文敏)
ukai at chromium.org
Wed Dec 2 23:49:23 PST 2009
I've question about thread to run Web Socket feedback from the protocol.
If server sends back handshake response and a data frame, and close
1) When client recognizes handshake response header, it changes readyState
to OPEN and queue a task to fire a simple event named "open".
2) Then client reads a data frame, and queue a task to fire a MessageEvent.
3) Then client recognizes the socket is closed, it changes readyState to
CLOSED and queue a task to fire a simple event named "close".
I'm wondering this process should be done on the same thread of the
code is processed. Thus, readyState is OPEN when it receives "open" event.
However, if it may run on the different thread, 1)-3) might be processed
receives "open" event.
Which is correct behavior?
It seems WebKit/Mac does former, and Chromium does latter, so
LayoutTests/websocket/tests/simple.html would fail with Chromium.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the whatwg