DescriptionMake sure to process WebSocket frames when closing a WebSocket
On a WebSocket the actual listening on the stream is causing the
processing of inbound frames to start. If the connection is closed
without ever being listened on, then a close frame from the other end
will not be processed. In this case the timeout of waiting for a
close from the other end will always be hit.
If you are _only_ using the WebSocket connection in one direction it
seems a bit artificial to have to listen on the stream to even process
the close frame.
This change will make sure the stream is listened to when closing a
WebSocket.
This is a breaking change. Before you could close and then
listen. With this change that sequence will throw on the listen. This
is reflected in the changes that was needed for the tests.
R=kustermann@google.com, lrn@google.com
BUG=
Committed: https://code.google.com/p/dart/source/detail?r=45679
Patch Set 1 #
Total comments: 6
Patch Set 2 : Addressed review comments #
Messages
Total messages: 4 (0 generated)
|