One of the issue for us at Novell Vibe, is that it's not trivial, or even easy, to integrate our user access control with existing XMPP infrastructure products - causing some gaps that we weren't fond of. Along with this, XMPP was additional infrastructure that requires both hardware resources and expertise, adding to the complexity and cost of deployment (rather than utilizing existing HTTP infrastructure).
/Ian On 11/17/2010 07:35 AM, Dave butlerdi wrote: > Perhaps, however some of us have substantial development efforts that, at > least in our case, > leverage XMPP. In the end it really does not matter what decisions are taken > and several > protocols may be developed/deployed/available however there has been effort > using the XMPP proto. > > Secondly, I have a difficult time understanding the difficulty in setting up > and integrating XMPP > servers. If this truly is a problem would it not be wise just to clean this up > making it substantially easier for non XMPP folks ? > > > > Regards > > Dave Butler > > -- > 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. -- 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.
