I would go with XMPP, just for fact that most current foundation server projects already works as XMPP server components, implementing c/s would be easier, also XMPP have lot of ready to go features that can be used on wave. Besides, Wave is already one foot on XMPP, why complicate life to making c/s in completely different format then s/s, it would be some sort of "understandable island" for XMPP clients in there network. Whatever happens, i think XMPP will end up having wave c/s support anyway, if not by this team then by others, existence of wave components on it's network just yell to do that.
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
