Nelson, There has been large debate on XMPP in wave. The general complaint is that the protocol is to verbose. My two cents are that one of the main points of XMPP was a verbose XML human readable protocol with standard extension mechanisms. However wave uses protobufs and base64 encodes all the data in the XMPP stanzas. The data exchanged by wave is not human readable, xml based, or part of the XMPP standard. That defeats the purpose of using the XMPP standard in the first place. In my opinion this basically relegates XMPP to just a delivery envelope, and one that adds on a lot of overhead.
Also XMPP's dependance on long lived TCP connections to maintain the xml stream, there are difficulties providing services to clients that are frequently disconnected. For these reasons there is talk of adding a "raw" http transfer mechanism for federation. Until that is worked out I would hesitate to entertain the idea of injecting XMPP in to the c/s protocol. ~Michael On Apr 9, 2011, at 2:51 PM, Nelson Silva wrote: > XMPP over websockets was proposed as a draft > (http://tools.ietf.org/html/draft-moffitt-xmpp-over-websocket-00) and > ejabberd now has a sample module to support it: > > http://blog.superfeedr.com/xmpp-over-websockets/ > > Wouldn't it be great to use XMPP for both C/S and federation ? or is it too > verbose ? > > Just wanted to share this with the list. > > Regards, > > Nelson
