W3C home > Mailing lists > Public > whatwg@whatwg.org > June 2009

[whatwg] Issues with Web Sockets API

From: Drew Wilson <atwilson@google.com>
Date: Fri, 26 Jun 2009 14:01:44 -0700
Message-ID: <f965ae410906261401k1184e1bfkac46bbc22062f12e@mail.gmail.com>
On Fri, Jun 26, 2009 at 1:14 PM, Kelly Norton <knorton at google.com> wrote:

> One thing about postMessage that I'm curious about. Since it has to report
> failure synchronously by throwing an INVALID_STATE_ERR, that seems to imply
> that all data must be written to a socket before returning and cannot be
> asynchronously delivered to an I/O thread without adding some risk of
> silently dropping messages.


I don't think that's the intent of the spec - the intent is that
INVALID_STATE_ERR is sent if the port is in a closed state, not if there's
an I/O error after send. But Michael's right, I don't think there's any way
to determine that the server received the message - I guess the intent is
that applications will build their own send/ack protocol on top of
postMessage(), as you note.

-atw
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090626/e25c5429/attachment.htm>
Received on Friday, 26 June 2009 14:01:44 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:13 UTC