When I first started reading about how wave federation is implemented as an extension to xmpp, I mistakenly thought that the wave client- server protocol was an extension. Now I see the client-server goes through protobuf based rpc.
Take this with a grain of salt, as I'm pretty new to all this, but currently it appears to me that the way wave is implemented over xmpp is fairly heavy, in terms of hardware resources and software complexity, for the returns. In a nutshell, here's what I understand: The primary purpose of xmpp is to allow federation. For now, federation is implemented on top of xmpp as an xmpp component. This means the wave server communicates with the xmpp server over tcp with xmpp stanzas. This seems to introduce a potentially unneccessary overhead, in parsing/encoding the messages etc. Moreover, the necessity to use xmpp service discovery for connecting to remote wave-over-xmpp servers seems to be an artifact of the decision to federate by xmpp. Has anyone considered a more light-weight adoption of xmpp-based federation? For example, only the xmpp server-to-server stream setup could be implemented to validate certs of hosts in a network, determining the hosts and ports with wave specific SRV records. The rest of the wave- specific operations could be coded directly, perhaps even in protobufs. While I understand the desire to make use of existing software such as xmpp servers, and it's good to have wave federation over xmpp, my impression is that dedicated federation of wave servers without such heavy usage of the xmpp stuff is of interest as well. On a protocol design level, I'd like the design of a more direct dedicated protocol before a bridge over xmpp. Maybe I'm missing some things here, but can anyone more knowledgable comment? Thanks, 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 -~----------~----~----~----~------~----~------~--~---
