Based on my investigation so far, it would be possible to create a client/server protocol that is just a special case of the server/server federation protocol. Some of the benefits to using XMPP are: 1. Potential for significant shared code between client/server and federation in FedOne. 2. Authentication is already handled in XMPP so saves the need to add it to FedOne.
With federation FedOne used acknowledgments and a logarithmically increasing delay time for retransmits. The same will work for clients, but can be optimized by allowing the server to receive user presence notifications. It would be expected that an XMPP client would cache wavelet history and as such the server would only send new delta and respond to history and cert requests. -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 -~----------~----~----~----~------~----~------~--~---
