On Mon, Sep 7, 2009 at 2:08 PM, Sam Thorogood<[email protected]> wrote: > > +1 to Anthony's response. I don't really have anything else to add. > Writing a whole new transport layer (even one specially designed for > Wave) is arguably non-trivial :)
I don't think there'd be any reason to design a whole new transport, One could just define the protocol exactly like xmpp server-server streams, where the only allowed stanzas are those used in wave, but eliminate service discovery, replacing it with SRV records. That would eliminate the need for the extra communication step between the xmpp server and the component, and the need to do service discovery. It would free the protocol from the requirement of running an xmpp server but wouldn't support out of the box use of xmpp servers either. > > To comment on Tad's observations: our usage of XMPP is very different > than that of say, GTalk. We gain a lot from using XMPP as a protocol, Indeed, but it's a little strange if you think of trying to host wave without providing xmpp :) Scott > but we don't actually 'gain' any integration with existing services. > For instance, we don't even use traditional JIDs: messages aren't > delivered to [email protected], they're delivered to > wave.wavesandbox.com which interprets the messages (as deltas etc) and > maps the resulting wavelets to the server's users. > > (Please note that I'm not commenting on the idea of an integrated > experience, I'm just saying that this isn't the reason we've looked > into XMPP as the underlying protocol.) > > On Mon, Sep 7, 2009 at 16:27, Anthony Baxter<[email protected]> wrote: >> >> 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] >> >> > >> > > > > -- scott --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
