> Essientially if you did so the client would become a server, and have to be
> reachable 24 hours a day.

I probably should have been clearer about what I'm proposing. What I
should have said was that we can use the existing messages, but with
different semantics.
The s2s is more of a push model, with some request/response thrown in
and the assumption that the server is almost always on. For c2s a more
traditional pubsub model is needed.

Here's what I'm thinking of at the moment.
-- Client sends subscription requests to the wave server. The request
could contain the same information included in the current open
request.
-- The server sends new delta's as they arrive.
-- The client acknowledges receipt of deltas as they arrive.
-- The client requests history for wavelets. It has the option to
cache history locally so that it doesn't need to request as much
history during subsequent sessions.
-- The server would consider a client disconnected if it doesn't
receive an acknowledgment within a given time frame. In this case it
would clear all subscriptions from that client.
-- The client would request signer info as needed.
-- The client would unsubscribe prior to disconnect.

The server could optionally subscribe to the clients presence status
to get more timely notice of client disconnect.

The s2s doesn't actually use the XMPP server's pubsub service, it just
uses messages in the pubsub namespace. The same would be true with
c2s. The wave server would manage the subscriptions, not the XMPP
server.

The end result is that c2s would use all the same messages as s2s with
the addition of the subscribe/unsubscribe messages.

-Tad

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Wave 
Protocol" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/wave-protocol?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to