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

Re: [hybi] Reliable message delivery (was Re: Technical feedback.)

From: Scott Ferguson <ferg at caucho.com>
To: Justin Erenkrantz <justin at erenkrantz.com>
Cc: "hybi at ietf.org" <hybi at ietf.org>
Date: Wed, 03 Feb 2010 09:02:30 -0800
In-reply-to: <5c902b9e1002030855u13d07708pc6af886d00dc33ce at mail.gmail.com>
References: <06912AB8-D55D-46F4-AAEC-0A2146FB3BB8 at apple.com> <292090.96637.qm at web95403.mail.in2.yahoo.com> <5c902b9e1002030855u13d07708pc6af886d00dc33ce at mail.gmail.com>

Justin Erenkrantz wrote:

On Wed, Feb 3, 2010 at 8:54 AM, Mridul Muralidharan <mridulm80 at yahoo.com> wrote:

Is hybi expected to be limited only to javascript or even browser based clients ?
I was assuming other clients might also be interested in leveraging it ? (if nothing else, for async notifications on top of http).


As I have mentioned before, I am certainly interested in non-browser
applications.  -- justin

We're using it for server to server messaging (using the binary packetencoding) as well as non-browser clients.


-- Scott

_______________________________________________
hybi mailing list
hybi at ietf.org
https://www.ietf.org/mailman/listinfo/hybi

Follow-Ups:
- Re: [hybi] Reliable message delivery (was Re: Technical feedback.)
  - From: Salvatore Loreto

References:
- Re: [hybi] Reliable message delivery (was Re: Technical feedback.)
  - From: Maciej Stachowiak
- Re: [hybi] Reliable message delivery (was Re: Technical feedback.)
  - From: Mridul Muralidharan
- Re: [hybi] Reliable message delivery (was Re: Technical feedback.)
  - From: Justin Erenkrantz

Prev by Date: Re: [hybi] Reliable message delivery (was Re: Technical feedback.)
Next by Date: Re: [hybi] Websocket algorithmic specification
Previous by thread: Re: [hybi] Reliable message delivery (was Re: Technical feedback.)
Next by thread: Re: [hybi] Reliable message delivery (was Re: Technical feedback.)
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.