summaryrefslogtreecommitdiff
path: root/classes/Queue_item.php
AgeCommit message (Collapse)Author
2008-09-26path correct in require_once for memcachedEvan Prodromou
darcs-hash:20080926161824-5ed1f-b4fb53e5ca65bb099aabbba6ea60a13496f669a2.gz
2008-09-26prepend Memcached_DataObject require with INSTALLDIREvan Prodromou
darcs-hash:20080926161540-5ed1f-2e9dc6f2297c612208214a6d52f36ce0dd7aa4de.gz
2008-09-26caching layer for DB/DataObjectEvan Prodromou
I added a new class, Memcached_DataObject, that will (optionally) fetch data out of a memcached server if it's available. This only works on 'staticGet'. Methods that write to the database (insert, update, delete) will clear and set the cache correctly, too. darcs-hash:20080926160941-5ed1f-922de078b4c1941853ad014edf9a17fae486f8cf.gz
2008-08-30log transport when claiming a noticeEvan Prodromou
darcs-hash:20080830054933-84dde-58cc7aa6947612cda9987d532d85d9dd81e32410.gz
2008-08-27$this->log to common_log in Queue_itemEvan Prodromou
darcs-hash:20080828004503-84dde-c406172d750d0a5452d5cc62ecd7b27db381c575.gz
2008-08-27change queue_item to use a compound primary keyEvan Prodromou
Breaking up to use multiple queue handlers means we need multiple queue items for the same notice. So, change the queue_item table to have a compound pkey, (notice_id,transport). darcs-hash:20080827211239-84dde-db118799bfd43be62fb02380829c64813c9334f8.gz
2008-08-27break up monolithic xmppdaemon into multiple queue handlersEvan Prodromou
Eventually, the poor xmppdaemon has become overloaded with extra tasks. So, I've broken it up. Now, we have 5 background scripts, and more coming: * xmppdaemon.php - handles incoming XMPP messages only. * xmppqueuehandler.php - sends notices from the queue out through XMPP. * smsqueuehandler.php - sends notices from the queue out over SMS * ombqueuehandler.php - sends notices from the queue out over OMB * xmppconfirmhandler.php - sends confirmation requests out over XMPP. This is in addition to maildaemon.php, which takes incoming messages. None of these are "true" daemons -- they don't daemonize themselves automatically. Use nohup or another tool to background them. monit can also be useful to keep them running. At some point, these might become fork()'ing daemons, able to handle more than one notice at a time. For now, I'm just running multiple instances, hoping they don't interfere. darcs-hash:20080827205407-84dde-97884a12f5f4e54c93bc785bd280683d1ee7e749.gz
2008-07-19add a transport flag to queue itemsEvan Prodromou
darcs-hash:20080719140906-84dde-9fcac26ee544ad53091808256f70b1745ac27a70.gz
2008-07-15replies from people you're not subscribed to over JabberEvan Prodromou
darcs-hash:20080715195513-84dde-454419c971015be385d9c4c35f7acbee419031f9.gz
2008-07-09Merge conflicts and kill a whole lot of trailing whitespace on lines.Mike Cochrane
darcs-hash:20080709224630-533db-b5399baef280133858dac9b89c2cd6a2aba9f861.gz
2008-07-04don't treat notice_id like a sequenceEvan Prodromou
darcs-hash:20080704082418-84dde-5f314d3f0c72756f480599913a4aab6c0404dcc6.gz
2008-07-04add a queued notice itemEvan Prodromou
darcs-hash:20080704040746-84dde-36803f820ea7c238613cf5728c59a18ff1eb442d.gz