xmpp vs. long polling vs. pubsubhubbub

[briandunnington]

when the notify.io discussions were getting off the ground, it sounded
like XMPP was going to be the delivery method of choice since 1) it
was made for 'push' type communication, and 2) Yapper was already
built on top of it.

when checking out your Hookah project, it says that it supports
webhooks (POST), PubSubHubbub, and long polling instead. i think you
said in another post that you were leaning toward long polling at the
moment, but am i correct in assuming you will want to support various
transports and thus the Hookah library?

you probably have already seen it, but here is a link to a
PubSubHubbub-to-XMPP gateway running on App Engine that looks
interesting: http://grack.com/blog/2009/09/09/pubsubhubbub-to-xmpp-gateway/
- it allows the simplicity of PubSubHubbub, but handles the 'how do i
get it to the desktop' portion as well. and since it runs on App
Engine, it fits in with the POSS model.

just thought i would share it for those that had not seen it yet.

[Abi Raja]

Yes! Silent diving seagulls was using XMPP too. But for some reason, we decided to switch from XMPP to long polling (I forget Jeff's reasons..)

I don't see why we would want to support various transports because this is internal to notify.io. Websites that use notify.io to send desktop notifications to their users don't know that we are in fact using XMPP to send those notifications, they only see the REST API. Similarly, the users don't care either. So, we need to figure out what is the right transport for us but multiple supports seems unneccesary to me.

- Abi

2009/9/29 briandunnington <briandu...@gmail.com>

[Jeff Lindsay]

Yeah, I mean ... at first I wanted to use XMPP because it was the obvious choice ... and even though it's almost overkill and sometimes troublesome and weird, this "obvious choice" thing I've seen all over the place. PBworks is adding real-time collaboration using XMPP/Bosh ... and even though they're weary of XMPP, they know it works because others have done it. I think "obvious choice" is pragmatic but not progressive, and since I felt like we could really go either way (it really doesn't matter at the end of the day), I should actually try to do it the not-as-obvious-but-perhaps-could-be-if-proven way. Especially if I've been writing a lot of code for this way, it would be silly not to leverage/prove these other projects I'm involved in.

So that's all. Also, I'm not using Hookah currently because I get caught up generalizing to easily. We may use Hookah at some point, but for now it's a custom codebase that's based on Hookah/Twisted/etc (that's pretty simple).

-jeff

--
Jeff Lindsay
http://webhooks.org -- Make the web more programmable
http://shdh.org -- A party for hackers and thinkers
http://tigdb.com -- Discover indie games
http://progrium.com -- More interesting things