Comments on: Beyond REST, or Beyond XMPP? Both? The Q&A

By: tecosystems » Three Things That People Get Wrong About Cisco’s Jabber Acquisition

Wed, 24 Sep 2008 02:40:20 +0000

[...] long bets, Kellan and Rabble’s presentation, and AMQ vs XMPP. As you might have guessed from the interview I did with ex-Jabber CTO and new Cisco employee Joe Hildebrand a few months [...]

By: The Burgeoning Openly Owned Web » links for 2008-09-06

The Burgeoning Openly Owned Web » links for 2008-09-06 — Sat, 06 Sep 2008 10:16:23 +0000

[...] tecosystems » Beyond REST, or Beyond XMPP? Both? The Q&A Nice introduction to XMPP and all the XEPs (tags: xmpp) [...]

By: andy.edmonds.be › links for 2008-09-06

andy.edmonds.be › links for 2008-09-06 — Sat, 06 Sep 2008 10:05:18 +0000

[...] tecosystems » Beyond REST, or Beyond XMPP? Both? The Q&A Nice introduction to XMPP and all the XEPs (tags: xmpp) This was written by andy. Posted on Saturday, September 6, 2008, at 11:05 am. Filed under Delicious. Bookmark the permalink. Follow comments here with the RSS feed. Post a comment or leave a trackback. [...]

By: JabberWerx AJAX | alexking.org

JabberWerx AJAX | alexking.org — Fri, 05 Sep 2008 17:29:43 +0000

[...] has a great Q&A on this. [...]

By: Paper tigers and hidden dragons » Untangled

Paper tigers and hidden dragons » Untangled — Thu, 04 Sep 2008 04:48:42 +0000

[...] certainly gave a very entertaining talk and one that spilled over into the blogosphere in posts by Stephen O’Grady, Joshua Schachter, and Debasish [...]

By: Jabber Filaments Blog » Blog Archive » XMPP and (not versus) REST

Jabber Filaments Blog » Blog Archive » XMPP and (not versus) REST — Fri, 01 Aug 2008 19:30:44 +0000

[...] on vacation or haven’t yet added the feeds at Redmonk to your reader, you may have missed an interesting discussion about the OSCON presentation Beyond REST? Building Data Services with XMPP. As is often the case [...]

By: Joe Hildebrand

Joe Hildebrand — Thu, 31 Jul 2008 22:36:14 +0000

Charles: the clients connect to the server.

If you’re allowed (or can be approved) to connect outbound on 5222/tcp, then you’re done.

Alternately, you can run your server on port 443 and use HTTP CONNECT to get through many proxy servers. If you can’t do that, you can always fall back on BOSH.

By: Joe Hildebrand

Joe Hildebrand — Thu, 31 Jul 2008 21:03:39 +0000

Most of the queuing protocols are not well-specified or standardized, and do not have Internet-scale addressing. AMQP may be the exception, but it has not been as widely-implemented yet. As well, many of the queueing protocols have been optimized for bank-transaction style guaranteed delivery. There are a whole class of problems for which this level of overkill has too great an impact on latency.

By: Charles

Charles — Thu, 31 Jul 2008 15:58:34 +0000

Cool article… Question: How would XMPP clients get through firewalls in a server to client scenario (I understand implications of server to server APIs)? That’s something that I have to address in my work unfortunately.

By: Geoff Watts

Geoff Watts — Thu, 31 Jul 2008 14:44:51 +0000

It really seems to me that pushing XMPP (an ‘orrible stateful chat protocol) into service for what is essentially cluster-IPC is a bit of misadventure.

Seems like the XMPP for IPC trend is just re-inventing message queueing. In fact, when I saw the slide deck written by the guy from Engine Yard, it occured to me that maybe he’d never heard of message queues!

I keep reading about friendster polling flickr, surely this could be sorted out with an API exposed over some kind of MQ?

ActiveMQ exists, so does AMQP. Maybe someone needs to create a slide deck and champion them a bit.