There are certainly few things that wave fedone server implementation is different from usual XMPP component implementation. I tend to assume that it is to avoid answering scalability question of XMPP server installation. When you have two parts to the whole picture (XMPP server and Wave Provider component) fedone implementation minimised the dependency of XMPP server entirely to the point that it's not really used for client/server interaction.
Although one would argue it's completely different demographic of traffic size and frequency, wonder how google chat and other jabber server implementation is done. J On Wed, Mar 3, 2010 at 5:13 AM, John Barstow <[email protected]> wrote: > Personally I'd be inclined to use BOSH (XMPP over HTTP) as we already > know how to send deltas via XMPP. > > -- > 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.
