Comments on: Beyond REST? Building data services with XMPP

By: marcus

marcus — Wed, 02 Sep 2009 08:24:37 +0000

the slides are gone

By: Beyond REST? XMPP — Matt Mullenweg

Beyond REST? XMPP — Matt Mullenweg — Sat, 02 Aug 2008 17:48:12 +0000

[...] Beyond REST? Building data services with XMPP. Pretty fascinating stuff. (4) PreviousPost NextPost [...]

By: On Talks - Laughing Meme

On Talks - Laughing Meme — Thu, 31 Jul 2008 07:31:48 +0000

[...] feedback on the Beyond REST talk has been immensely gratifying, the overwhelming positive response, and the engaged critiques. [...]

By: tecosystems » Beyond REST, or Beyond XMPP? Both? The Q&A

tecosystems » Beyond REST, or Beyond XMPP? Both? The Q&A — Thu, 31 Jul 2008 04:03:09 +0000

[...] Sam Ruby making it one of his long bets to Evan Henshaw-Plath and Kellan Elliott-Mcrea’s presentation at OSCON last week. What is it about XMPP that’s making it, like Hansel, so hot right now? [...]

By: Marc’s Voice » Blog Archive » final July ‘08 blogging

Marc’s Voice » Blog Archive » final July ‘08 blogging — Wed, 30 Jul 2008 20:41:38 +0000

[...] Beyond REST? Building data services using XMPP [...]

By: Julien

Julien — Tue, 29 Jul 2008 15:21:31 +0000

Kellan, I sent you an email about this presentation and a project that I have… have you received it?

By: Antonio

Antonio — Mon, 28 Jul 2008 18:49:42 +0000

K—

This was the most thought-provoking presentation I've seen in a while. I am bummed to have missed OSCON just because of this.

By: Emil Hesslow

Emil Hesslow — Mon, 28 Jul 2008 11:10:37 +0000

Kellan: Of cause. The final parts of the Masters Thesis is a report and a presentation. But because the report would probably contain a lot of information that nobody care about I have thought about doing a light version of the report. But at least the normal report will be published online.

By: Kellan

Kellan — Mon, 28 Jul 2008 01:09:20 +0000

Emil, neat. When you post something publicly about your work, let me know.

By: Kellan

Kellan — Mon, 28 Jul 2008 01:08:41 +0000

Marc, yup very well aware of Gnip. I’ve been in chatting with Eric about architecture and design of Gnip since December.

By: Marc Brooks

Marc Brooks — Sun, 27 Jul 2008 18:35:51 +0000

GNIP implements HTTP callback for most social feeds. http://www.gnipcentral.com/

By: Beyond REST? XMPP :: Sam’s random musings

Beyond REST? XMPP :: Sam’s random musings — Sat, 26 Jul 2008 17:31:29 +0000

[...] Beyond REST? Building data services with XMPP. Pretty fascinating stuff. [...]

By: Emil Hesslow

Emil Hesslow — Fri, 25 Jul 2008 09:18:55 +0000

Nice slides, wish I could have heard the talk.

I'm going to college in Sweden and right now I'm doing my Masters thesis and I'm looking into how to use XMPP as public API for a Swedish company. And how I designed it is exactly the same as yours (except the OAuth part which I'll probably add).

Really nice to see that someone else is having the same ideas.

By: joshua

joshua — Thu, 24 Jul 2008 21:59:05 +0000

Indeed – for big service to big service, XMPP firehose is the only way to go. But callbacks are better for most everything smaller than that, I think.

By: Kellan

Kellan — Thu, 24 Jul 2008 20:46:14 +0000

HTTP callbacks gets you something similar.

Personally, I don’t like the performance characteristics of HTTP callbacks as the service provider, and but for the “quantum” end of the scale web hooks work great. Not so much for the relativistic scales. (unless you’re running non-stock Web servers)

I think we’ll see XMPP-to-HTTP-callback proxies, I just don’t want to run them

By: joshua

joshua — Thu, 24 Jul 2008 19:05:15 +0000

I wrote my thoughts up a bit more clearly at http://joshua.schachter.org/2008/07/beyond-rest.html

By: joshua

joshua — Thu, 24 Jul 2008 16:18:39 +0000

Another interesting solution would be callbacks -- this was what I wanted to do for delicious. push a single URL up to the service, occasionally, and then get RSS individual item fragments POST'd back to you.

Something like del.icio.us/subscribe?resource=/joshua&callback=http://my.webapp/endpoint or similar.

I even came up with a witty acronym for it.

This is probably an easier solution for people who are interested in only a very small subset of updates, like if I wanted to have updates for my account get pushed to my blog.

By: Kellan

Kellan — Thu, 24 Jul 2008 14:23:06 +0000

@kael: I’d like to see someone tease out what the architecture would look like if you were to use the Ejabberd-AtomPub module. Part of what I like about the roll your own component approach is it gets the majority of the logic into something I deeply understand running, scaling, and monitoring as fast as possible.

@Christoper: so far its just an idea, but I tend to agree with you about intermediaries are sub-optimal, which is a conversation I’ve been having with bpm140 since before they launched

By: Christopher Clay

Christopher Clay — Thu, 24 Jul 2008 10:28:13 +0000

Good stuff. This would be a much better way of solving the polling issue than by introducing an intermediate between providers and consumers, as Gnip is doing. Is the Flickr case study real? Does the XMPP service exist yet, is it under development, or just an idea so far?

By: kael

kael — Thu, 24 Jul 2008 09:38:49 +0000

It's great to see XMPP emerging.

Have you considered the mapping of Pubsub to AtomPub like with the Ejabberd-AtomPub module ?

Also, after OAuth over XMPP, there could be OpenID over XMPP with XEP-0070 authentication and even then OpenID interchange over XMPP.