This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24824 - [WebSocket] Add note saying close() is graceful
Summary: [WebSocket] Add note saying close() is graceful
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-26 18:04 UTC by Takeshi Yoshino
Modified: 2014-02-28 00:39 UTC (History)
2 users (show)

See Also:

Attachments

Description Takeshi Yoshino 2014-02-26 18:04:17 UTC 
In HyBi list, some people wondered if close() may interrupt ongoing "Send a WebSocket Message" for a large message or not. Especially, about the API spec, people wondered if the data "queued" has any implication that they stay unsent to network and closing handshake may jump in.

http://www.ietf.org/mail-archive/web/hybi/current/msg10480.html

It's good if there's some note saying that when close() is called, closing handshake actually happens after flushing all data for preceding send() calls.
Comment 1 Ian 'Hixie' Hickson 2014-02-28 00:39:32 UTC 
Hopefully this clarifies it enough, reopen otherwise!
Comment 2 contributor 2014-02-28 00:39:55 UTC 
Checked in as WHATWG revision r8516.
Check-in comment: Clarify that close() doesn't drop earlier sent() images.
http://html5.org/tools/web-apps-tracker?from=8515&to=8516