- From: <bugzilla@jessica.w3.org>
- Date: Tue, 01 Nov 2011 16:48:17 +0000
- To: public-webapps@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14660 Summary: [Editorial] Clarification for CLOSING in Garbage Collection Product: WebAppsWG Version: unspecified Platform: PC OS/Version: Windows NT Status: NEW Severity: normal Priority: P2 Component: WebSocket API (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: brian.raymor@microsoft.com QAContact: member-webapi-cvs@w3.org CC: mike@w3.org, public-webapps@w3.org Since the W3C WebSocket API was clarified to reflect that onmessage is only called during the OPEN readyState (14474 - Make it possible to close a connection in such a manner that all subsequent events are suppressed), there are corresponding editorial changes required in Section 9 Garbage Collection: A WebSocket object whose readyState attribute's value was set to OPEN (1) or CLOSING (2) as of the last time the event loop started executing a task must not be garbage collected if there are any event listeners registered for message events, error, or close events. should differentiate between OPEN and CLOSING: A WebSocket object whose readyState attribute's value was set to OPEN (1) as of the last time the event loop started executing a task must not be garbage collected if there are any event listeners registered for message events, error, or close events. A WebSocket object whose readyState attribute's value was set to CLOSING (2) as of the last time the event loop started executing a task must not be garbage collected if there are any event listeners registered for error or close events. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Received on Tuesday, 1 November 2011 16:48:23 UTC