W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2012

[Bug 17262] send function should have async interface

From: <bugzilla@jessica.w3.org>
Date: Tue, 10 Jul 2012 21:35:40 +0000
Message-Id: <E1Soi5s-000838-O2@jessica.w3.org>
To: public-webapps@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17262

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
                 CC|                            |ian@hixie.ch
         Resolution|                            |WORKSFORME

--- Comment #22 from Ian 'Hixie' Hickson <ian@hixie.ch> 2012-07-10 21:35:40 UTC ---
I don't understand what this bug has to do with the WebSockets API. The send()
method in WebSockets is already implementable in a completely async manner.
It's up to the browser to get a copy-on-write reference to the underlying data,
but that's an implementation detail.

-- 
Configure bugmail: https://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, 10 July 2012 21:35:41 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:53 GMT