"Ping" waves are not special as far as the federation protocol is concerned. We are working on documentation that explains the document model and document schema in greater detail. You can see some docs at http://www.waveprotocol.org/draft-protocol-specs/wave-conversation-model, though it does not deal with ping waves. (Currently we add a special data document to a wavelet to indicate the presence of a ping, with the data document containing meta information. Note that this may change in future, and will hopefully be fully documented soon).
On Mon, Nov 16, 2009 at 1:53 PM, Daniel Spiewak <[email protected]> wrote: > > In the Wave client, it is possible to "Ping" a user. This starts a new > wave with that user. It's a perfectly ordinary wave, except that it > starts iconified at the top and then "special expanded" (with the down- > arrow). This behavior is a little different from normal wave delivery, > which can also start iconified, but never auto-expands. > > My question is: how does Wave track the difference between "ping > waves" and regular waves? Is that just internal to Google's client/ > server, or is there something in the Fed protocol that we need to > worry about? > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
