I've been wondering the same thing. The XMPP protocol overhead for small blips is around 50%. Plus the 25% increase in size due to the Base64 encoding. That adds up. It's possible that bandwidth isn't as much of a concern as it used to be, but still, a 50-75% reduction in message size is no small matter.
The server to server protocol is already designed, the only thing left is server discovery. And that can mimix the XMPP server discovers. Just use SRV records like _wave._tcp.acmewave.com. So the question is, what does XMPP provide that makes the overhead (protocol and infrastructure) worth it? One possibility is that Google already has an XMPP infrastructure in place and in use for their chat services. So maybe it makes sense from their point of view to just leverage what they already have. Plus I'm sure they plan to integrate XMPP chat and gmail with wave. So chats and e-mails will appear in waves (and probably vice versa). The transition to wave will be much easier if wave users can still interact with non-wave users. -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 -~----------~----~----~----~------~----~------~--~---
