On Wed, Feb 25, 2009 at 10:06 AM, Alexander Gnauck <[email protected]> wrote:
>> Why isn't this protocol important to Web communities? > > I don't have the answer to your question. In part I've got it ;) It's just in part due to technical issues or vision about functionalities. Yep, it's not trivial to setup a server for handling millions of concurrent connections and I think that Facebook just said that they were using XMPP, but actually their doing something of much simpler. If you take a look at how the chat thing is implemented you realized that it's very basic. All the presence stuff if just a poll with a request per minute asking "who's online?", while chats are based on comet requests on a sort of per-conversation pubsub topics. Behind that I don't see any XMPP infrastructure ad I'd be surprised to see it soon. Why? The reason is the business model: if you are Facebook and you serve billions of page views you can't afford allowing people to access the same functionalities with clients different from the web browser, since you lose the main value you have: the capability of controlling the display of the page and insert ads. Before opening to the federation, they must find a value in it. -- Fabio Forno, Ph.D. Bluendo srl http://www.bluendo.com jabber id: [email protected]
