[Bug 17264] Add attributes to use ping/pong frames effectively

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17264

--- Comment #10 from Takashi Toyoshima <toyoshim@chromium.org> 2012-06-01 06:46:36 UTC ---
As Ian said at #7, we can implement application specific ping/pong at the
subprotocol level.
But, it will reduce opportunity to use Blob and ArrayBuffer effectively.
Because sending a large file as a Blob will suspend subprotocol level
ping/pong, and it will fire timeout easily.

Of course we can create another special WebSocket instance for ping/pong. But,
no one assure that other WebSocket connections are sanity when ping/pong
connection is alive. If we can use multiplexing, situation will be improved.
But no one know which connections actually share the one TCP connection after
all.

Protocol level ping/pong might be primitive and simple. But it can be injected
in the middle of a fragmented message. It means that when application send a
large data, ping/pong frames can be handled periodically. This is a big
motivation to use protocol level ping/pong frames.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Friday, 1 June 2012 06:46:39 UTC