[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [hybi] web socket protocol in "last call"?

From: Julian Reschke <julian.reschke at gmx.de>
To: Maciej Stachowiak <mjs at apple.com>
Cc: "hybi at ietf.org" <hybi at ietf.org>
Date: Thu, 29 Oct 2009 06:07:33 +0100
In-reply-to: <5214ACB4-16C9-43BC-9C86-ACA330A9BFDC at apple.com>
References: <4AE7F0AE.1000102 at gmx.de> <Pine.LNX.4.62.0910280740540.25608 at hixie.dreamhostps.com> <4AE7FFC4.8050405 at gmx.de> <4AE806AA.60901 at ericsson.com> <Pine.LNX.4.62.0910280938560.25608 at hixie.dreamhostps.com> <4AE86513.4060600 at ericsson.com> <3a880e2c0910281301j5d1e4cdclfe2391b28eadda0e at mail.gmail.com> <5214ACB4-16C9-43BC-9C86-ACA330A9BFDC at apple.com>

Maciej Stachowiak wrote:

...
WebKit has an implementation of the WebSocket API and protocol inprogress. We do not anticipate that work reaching a freeze point in thevery near future. We'll think about taking appropriate measures to avoidlocking in the protocol when we ship, to give the IETF Working Group achance to define the protocol.
...


Thanks for the clarification!

BR, Julian

References:
- [hybi] web socket protocol in "last call"?
  - From: Julian Reschke
- Re: [hybi] web socket protocol in "last call"?
  - From: Ian Hickson
- Re: [hybi] web socket protocol in "last call"?
  - From: Julian Reschke
- Re: [hybi] web socket protocol in "last call"?
  - From: Salvatore Loreto
- Re: [hybi] web socket protocol in "last call"?
  - From: Ian Hickson
- Re: [hybi] web socket protocol in "last call"?
  - From: Salvatore Loreto
- Re: [hybi] web socket protocol in "last call"?
  - From: Infinity Linden (Meadhbh Hamrick)
- Re: [hybi] web socket protocol in "last call"?
  - From: Maciej Stachowiak

Prev by Date: Re: [hybi] web socket protocol in "last call"?
Next by Date: [hybi] Proposed Charter for HyBi WG (rev.3)
Previous by thread: Re: [hybi] web socket protocol in "last call"?
Next by thread: Re: [hybi] web socket protocol in "last call"?
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.