On Wed, Aug 13, 2008 at 12:57 PM, Evan Prodromou <[EMAIL PROTECTED]> wrote: > So, one of the key changes I want to make in the Laconica codebase is moving > us from a CMS model to a messaging model. That means that we stop treating > each notice as a document that is accessed from one location over and over, > and more like a message, which gets duplicated and moved around the system. > (One such place, of course, is permanent storage.) > > There are a couple of key elements to this: > > 1) Queues. Our entry points for notices (Web, email, sms, IM, API) need to > stop doing all the routing for messages. Instead, they should push the > notice into a primary queue, and other processes will copy it into further > queues for further processing. I've got a boxes-and-lines diagram here, with > boxes representing queues and circles representing processes that: > > http://laconi.ca/trac/attachment/wiki/Queues/laconica_queues.png > > Enabling tool here is going to be RabbitMQ, Apache Qpid, or ActiveMQ. Or > another Open Source queue manager -- Twitter apparently uses Starling, but > they've been bumping into some upper limits on that tool, apparently.
I would suggest looking into RabbitMQ - it has XMPP interfaces and is very stable (unlike my current nemesis at Seesmic - ActiveMQ) -- --- Bear [EMAIL PROTECTED] (work) [EMAIL PROTECTED] (jabber & email) http://code-bear.com/bearlog (weblog) PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29 _______________________________________________ Laconica-dev mailing list [email protected] http://mail.laconi.ca/mailman/listinfo/laconica-dev
