Hi, On Fri, Feb 12, 2010 at 3:56 AM, Peter Saint-Andre <[email protected]> wrote: > On 2/11/10 8:43 PM, Tim Julien wrote: >> 4. Support IQ > > Heh, yes. My understanding is that Facebook Chat is not a native XMPP > implementation, and that their XMPP features are implemented in a > gateway or a client connection manager of some kind. Unfortunately, > their backend system strips out all sorts of interesting data. Perhaps > they'll fix that in the coming months.
Exactly. They have a presentation somewhere about this, can't find it at the moment. The XMPP interface is a minimalist XMPP interface to their current HTTP-based chat. I would bet that the current idea is to provide a XMPP interface to their HTTP chat, not to provide a XMPP service. Its a subtle difference but it should help understand that the features they will add will always be restricted to the capabilities of the HTTP chat. So I don't believe we will see IQ-routing, and other stuff like that, until something like is that is needed to implement some feature they launch on the HTTP side of things. IMHO, the biggest reason for the XMPP interface is federation. And in that regard, I agree with Peter: first they crawl, then they walk. Bye, -- Pedro Melo http://www.simplicidade.org/ xmpp:[email protected] mailto:[email protected] _______________________________________________ JDev mailing list Forum: http://www.jabberforum.org/forumdisplay.php?f=20 Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
