BOSH is a way of doing XMPP over HTTP. So doing wave federation over XMPP over BOSH seems a bit redundant. We have federation over XMPP, we're adding federation over HTTP.
Some of the benefits of federation over HTTP are: 1. No more need to Base64 encode the messages. 2. The request/response model of HTTP obviates the need to add message acknowledgment to the existing XMPP federation transport. 3. Removes the need to install and configure an XMPP server in order to federate. 4. Integrates better with existing web infrastructure (e.g. operate behind apache server using ajp, integrate with web caches, etc...). There's nothing wrong with XMPP, it's great for what it does. But, besides the server discovery bit, I never understood why the wave team chose to use XMPP in the first place. Federation seemed to be "wedged" on top of XMPP. It didn't seem very efficient. Raw sockets whould have made more sense. The key take-away here is that XMPP based federation isn't being removed, it's just getting a little competition :-) -Tad On Wed, Nov 17, 2010 at 4:38 PM, [email protected] < [email protected]> wrote: > I'm confused, why isn't XMPP over BOSH reasonable instead of a whole > new protocol? > > -- > 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]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > > -- 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.
