- From: <bugzilla@jessica.w3.org>
- Date: Fri, 12 Aug 2011 07:31:05 +0000
- To: public-webapps@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13763
Summary: The WebSocket API should provide a polling mechanism
too. Only event based capture messages is not good
because if a method in a JS-Class send a message the
reply arrive in the event handler. The event handler
has no access (if no global var exists) to th
Product: WebAppsWG
Version: unspecified
Platform: Other
URL: http://www.whatwg.org/specs/web-apps/current-work/#the
-websocket-interface
OS/Version: other
Status: NEW
Severity: normal
Priority: P3
Component: WebSocket API (editor: Ian Hickson)
AssignedTo: ian@hixie.ch
ReportedBy: contributor@whatwg.org
QAContact: member-webapi-cvs@w3.org
CC: mike@w3.org, public-webapps@w3.org
Specification:
http://www.whatwg.org/specs/web-apps/current-work/complete/network.html
Multipage: http://www.whatwg.org/C#the-websocket-interface
Complete: http://www.whatwg.org/c#the-websocket-interface
Comment:
The WebSocket API should provide a polling mechanism too. Only event based
capture messages is not good because if a method in a JS-Class send a message
the reply arrive in the event handler. The event handler has no access (if no
global var exists) to the class instance who send the request. With a polling
mechanism the class instance can wait for a reply and with webworkers there
should be no problem with waiting and polling.
Posted from: 93.217.122.57
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101
Firefox/5.0
--
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 Friday, 12 August 2011 07:31:06 UTC