Speaking purely for myself, using an XMPP component made implementation of the federation side so very very much easier. I can let the XMPP server handle a lot of the messy lower level stuff, like TLS and the like. It also slots into existing infrastructure - both ours, and anyone else who's running an XMPP server.
On Mon, Sep 7, 2009 at 15:27, Brian May<[email protected]> wrote: > > On Sun, Sep 06, 2009 at 10:10:38PM -0700, Tad Glines wrote: >> 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. > > Wave doesn't need to use XMPP to get this happening. > > e.g. see twitter support in Google Wave. > > Maybe they felt reusing an existing protocol might be better received then > inventing a new one from scratch? > -- > Brian May <[email protected]> > > > > -- 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 -~----------~----~----~----~------~----~------~--~---
