blog.lmorchard.com

passing the turing test since 1975

Interop: Movable Type IM-based pub/sub?

Even more gas is flowing - from andersja's blog: Movable Type notifications to Instant Messenger?

I really want to see this, and I want to see news aggregators exploit this - why poll a feed once an hour when you can just have the feed tell you to come 'n get it? Basic publish/subscribe model.

But the advantage Radio has over MT in this regard is this: Radio is a persistently running app/server/daemon thing. MT is a collection of scripts that does nothing until asked to run. Radio can connect to IM and stay connected. Something like MT would need to login to an IM service each and every time it wanted to ping. Maybe that's not such a big deal, really. I also have a hunch that there would be some difficulties with web hosting sites who don't really want customers emitting IMs from their CGIs. Maybe not a big deal either.

Just seems like an impedance mismatch, though.

What I'd like to see is something like this: An XML-RPC/SOAP <-> IM gateway. And then, eventually, I'd like to see a decentrallized P2P network with XML-RPC/SOAP entry points that can smoothly replace centralized resources that have XML-RPC/SOAP entry points, maybe using IM networks as one possible rendevous point. (Just remembered this project: JXTA Bridge. Mental note - play with JXTA again and poke at SOAP some more.)

shortname=ooobfa

Archived Comments

  • Sean Conner

    Why not use IRC? Decentralized, standard protocol, and *all* the DDoS zombies use it for communication. Okay, so it doesn't support XML-RPC/SOAP, but I'm still not fully convinced XML-RPC/SOAP is all it's cracked up to be. Come on, it's just a glorified CGI call. -spc (Or even NNTP! Surely you can do XML-RPC/SOAP calls via Usenet ... )
  • Shawn

    I hear what you're saying, Sean, but I think the answer to your question is "ubiquity." While IRC is popular among us old-timers, it has nothing on the mass popularity of IM.
  • l.m.orchard

    Hell, why choose? Use both and everything else available. Make a clean interface on the frontend with XML-RPC or SOAP, and rendevous with other agents via whatever channel is most convenient. Have an IRC server in mind? Meet up there. Netsplit? Bounce some IMs around. Jabber server down? Maybe try some JXTA. Sky falling everywhere but on a local known NNTP server, start posting messages to each other. Hmm.. have to think some more about this.
  • DJ

    An XML-RPC-to-IM gateway? How about this: http://www.pipetree.com/jabber/jrpc/httpgate/ - it's perhaps a start, or at least food for thought :-)
  • DJ

    I almost forgot - there's also this to add to the soup: http://www.pipetree.com/qmacro/2002/Jul/03#weblogspubsub
  • Mark Paschal

    Yeah, I see nothing wrong with using IRC, since it's suppose to be behind the scenes anyway, isn't it? For program to program pub-sub, anyway.
  • hgh

    good
  • carpet

    good websiet
  • baby blanket

    good websiet
  • rugs

    good websiet
LiveJournal largely ignored, but why?  Previous Outlining + IM = On Fire Next