Comments on: Facebook XMPP Server http://florianjensen.com/2009/11/16/facebook-xmpp-server/ making the world a better place! Fri, 26 Feb 2010 11:55:28 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Florian Jensen http://florianjensen.com/2009/11/16/facebook-xmpp-server/comment-page-1/#comment-11584 Florian Jensen Sat, 05 Dec 2009 16:25:48 +0000 http://florianjensen.com/?p=769#comment-11584 <a href="#comment-11579" rel="nofollow">@Ed Jolanski </a> Not yet :( @Ed Jolanski
Not yet :(

]]> By: Ed Jolanski http://florianjensen.com/2009/11/16/facebook-xmpp-server/comment-page-1/#comment-11579 Ed Jolanski Thu, 03 Dec 2009 16:03:59 +0000 http://florianjensen.com/?p=769#comment-11579 Who cares what server software they're using...did you figure out how LOG IN to it? Who cares what server software they’re using…did you figure out how LOG IN to it?

]]> By: Gerard Braad http://florianjensen.com/2009/11/16/facebook-xmpp-server/comment-page-1/#comment-11559 Gerard Braad Mon, 16 Nov 2009 17:28:41 +0000 http://florianjensen.com/?p=769#comment-11559 <a href="#comment-11551" rel="nofollow">@GR </a> The video of the slides is also available at: http://www.vimeo.com/6699769 @GR
The video of the slides is also available at: http://www.vimeo.com/6699769

]]> By: Sebastiaan Deckers http://florianjensen.com/2009/11/16/facebook-xmpp-server/comment-page-1/#comment-11558 Sebastiaan Deckers Mon, 16 Nov 2009 14:17:57 +0000 http://florianjensen.com/?p=769#comment-11558 Actually it's not that surprising the IDs are different. There could be any number of reasons for changing the way they are generated. I think most likely this helps to route packets more efficiently between nodes in their cluster. Similar to how the GTalk server rewrites resource identifiers for internal routing purposes. Also, as GR said, it wouldn't be the first time Facebook heavily modifies existing open source projects. They practically rewrote memcached to scale with their userbase. I see absolutely no reason to doubt ProcessOne's claim and the achievement of the Ejabberd team. Actually it’s not that surprising the IDs are different. There could be any number of reasons for changing the way they are generated. I think most likely this helps to route packets more efficiently between nodes in their cluster. Similar to how the GTalk server rewrites resource identifiers for internal routing purposes. Also, as GR said, it wouldn’t be the first time Facebook heavily modifies existing open source projects. They practically rewrote memcached to scale with their userbase. I see absolutely no reason to doubt ProcessOne’s claim and the achievement of the Ejabberd team.

]]> By: Florian Jensen http://florianjensen.com/2009/11/16/facebook-xmpp-server/comment-page-1/#comment-11556 Florian Jensen Mon, 16 Nov 2009 09:42:53 +0000 http://florianjensen.com/?p=769#comment-11556 Thanks for the slideshow. Haven't seen that one before. I just find it weird, that they would change the Message IDs. That looks like something very deep down in the server core. But hey, nothing is impossible :) Thanks for the slideshow. Haven’t seen that one before.

I just find it weird, that they would change the Message IDs. That looks like something very deep down in the server core.

But hey, nothing is impossible :)

]]> By: Bartosz Małkowski (bmalkow) 's status on Monday, 16-Nov-09 08:39:32 UTC - Identi.ca http://florianjensen.com/2009/11/16/facebook-xmpp-server/comment-page-1/#comment-11552 Bartosz Małkowski (bmalkow) 's status on Monday, 16-Nov-09 08:39:32 UTC - Identi.ca Mon, 16 Nov 2009 08:39:48 +0000 http://florianjensen.com/?p=769#comment-11552 [...] chat.facebook.com ? http://florianjensen.com/2009/11/16/facebook-xmpp-server/ a few seconds ago from [...] [...] chat.facebook.com ? http://florianjensen.com/2009/11/16/facebook-xmpp-server/ a few seconds ago from [...]

]]> By: GR http://florianjensen.com/2009/11/16/facebook-xmpp-server/comment-page-1/#comment-11551 GR Mon, 16 Nov 2009 07:25:16 +0000 http://florianjensen.com/?p=769#comment-11551 You realize that the process one folks said that a 'customized ejabberd' was used. And you also realize that Facebook engineers have said publicly that they are using eJabberd? Right? Of course they customized it, just like they have with other Open Source products that they use (e.g. memcached). See the Facebook engineers talk about it in the link provided in the Process One post. http://cufp.galois.com/2009/slides/PiroLetuchy.pdf So, in my opinion, if you are going to publicly 'call bullshit' on the Process One (and Facebook) folks, you should at least have provided some kind of verifiable evidence to back it up. You provided nothing. You realize that the process one folks said that a ‘customized ejabberd’ was used. And you also realize that Facebook engineers have said publicly that they are using eJabberd? Right? Of course they customized it, just like they have with other Open Source products that they use (e.g. memcached). See the Facebook engineers talk about it in the link provided in the Process One post.

http://cufp.galois.com/2009/slides/PiroLetuchy.pdf

So, in my opinion, if you are going to publicly ‘call bullshit’ on the Process One (and Facebook) folks, you should at least have provided some kind of verifiable evidence to back it up. You provided nothing.

]]> By: Akari (akari) 's status on Monday, 16-Nov-09 00:46:42 UTC - Identi.ca http://florianjensen.com/2009/11/16/facebook-xmpp-server/comment-page-1/#comment-11548 Akari (akari) 's status on Monday, 16-Nov-09 00:46:42 UTC - Identi.ca Mon, 16 Nov 2009 00:46:49 +0000 http://florianjensen.com/?p=769#comment-11548 [...] noticia de !jabberes: http://florianjensen.com/2009/11/16/facebook-xmpp-server/ [...] [...] noticia de !jabberes: http://florianjensen.com/2009/11/16/facebook-xmpp-server/ [...]

]]>