Hi, PubSub is really just a container format. It's quite arguable that in fact I was being a little too clever in how I used it.
A remote sender sends a history request when it's missing deltas. For instance, say a u...@remotedomain is first added at version 100 of the wave. That version will be sent in a wavelet update to remotedomain's server. Now, to apply that, the remotedomain server needs the (missing) history. It does a request for versions 0-99. Another case might be if a remote server is offline and misses an update(*). It can issue a history request for the missing deltas. (*) there's a whole separate issue of reliable delivery in this case, which we haven't implemented yet. Anthony On Tue, May 4, 2010 at 00:25, Tsvetelina <[email protected]> wrote: > Hello, > > I've been going over the wave protocol specs and I miss a detailed > information on how exactly Google Wave uses PubSub. I am really not > able to get the whole picture from the specs, so I would be grateful > to get some insights from you. > > It is also not really clear to me when and why certain messages are > send. For example, when exactly does a remote send a history request > to a host, and what does it have to do with pubsub? I hope someone > would have satisfying answers to these questions. > > Best regards, > Tsvetelina > > -- > 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. > > -- Anthony Baxter, [email protected] -- 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.
