> > Although I have not been closely following Wave recently, it seems to me > that the "XMPP madness" is not related to XMPP (it's really dead simple >
The "madness" is indeed related to how wave USES XMPP. XMPP by itself is fine. > to set up XMPP federations), but to security (getting the certs right, > etc.). It's not clear to me how swapping XMPP for HTTP is going to help > in that regard. > How many developers and sysadmins out there already succeeded in getting certs for HTTPS up and running compared to how many did get XMPP with certificates up and running? There is simply more HTTP knowledge out there than XMPP experience. Why do Pubsubhubbub and RSSCloud have more mind-share among web developers than XMPP-based pub/sub solutions? Simply because both build on infrastructure which is widely known and deployed. From a technical perspective, XMPP was up to the task. Greetings Torben > > On 11/17/10 5:30 AM, Torben Weis wrote: > > Hi, > > > > even the federation demo during the workshop failed because of some XMPP > > madness :-) It is simply too complicated to setup and use and not as > > widely deployed as XMPP-enthusiasts might believe. > > > > Furthermore, Wave is mainly sending base64 encoded ProtoBufs via XMPP. > > If you look very very closely at the current wave protocol, you will > > find out that wave (ab-)uses XMPP as a very dump transportation > > protocol. Except for discovery, there is little that XMPP provides to > > wave besides shipping bytes from A to B. So the "out of the box > > functionality" argument is not really true IMHO. > > > > To underpin my argument: For the HTTP federation protocol we just had to > > re-do the discovery. Everything else is basically unchanged. The fact > > that we could replace XMPP with HTTP rather easily shows that wave did > > not make any usage of specific XMPP features. XMPP is not good as a > > general purpose transport protocol. HTTP is. > > > > Greetings > > Torben > > > > > > > > 2010/11/17 Dave butlerdi <[email protected] <mailto:[email protected] > >> > > > > I really am having a difficult time understanding the aversion to > > XMPP. It adds so much > > functionality out of the box, is widely accepted and brings with it > > a large number of > > potential adopters. > > > > Why not just get the project up as close to what was there and then > > sub project the other transports. > > > > -- > > Regards > > > > Dave Butler > > > > -- --------------------------- Prof. Torben Weis Universitaet Duisburg-Essen [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.
