Re: [hybi] Intermediaries

[Greg Wilkins <[e-mail]>]

Kris,

+1 on supporting intermediaries.

I think it is important to at least allow intermediaries to cleanly
close connections without routine loss of messages and retry+idempotency
complications.

Multiplexing support is also key if intermediaries are going to
be capable of doing much intelligent stuff.

More in-line....


Kris Zyp wrote:
> * Subscription mechanisms defined in the protocol

I can't believe that I'm about to type this.... because I
really like subscription mechanisms....   With cometd/bayeux,
I think one of the biggest sources of confusion has been that
subscription is built into the protocol, so that while non-subscription
delivery is supported, people just don't get it and those that
don't want subscription are very anti the bayeux protocol.

So I would say approach subscription with caution... and
potentially specify it as a layer on top of the base protocol.

As you say, multicast is a big win for the subscription model
( as used Oort Cometd cloud).



> * HTTP cache updating 

Neat idea.   I also think that the bidirectional protocol
should be able to carry regular HTTP request/responses as
well.    It would be strange if you had a fully capable
bidirectional connection, but had to crack open another
TCP/IP connection just to get favicon.ico


You could almost consider that caching mechanism an
extension of the subscription mechanism.  If you
subscribed to favicon.ico you would be sent that
resource again whenever it updated.


cheers