Summary | Horde_Queue |
Queue | Horde Framework Packages |
Queue Version | HEAD |
Type | Enhancement |
State | Assigned |
Priority | 1. Low |
Owners | chuck (at) horde (dot) org |
Requester | chuck (at) horde (dot) org |
Created | 08/30/2008 (6101 days ago) |
Due | |
Updated | 05/27/2009 (5831 days ago) |
Assigned | |
Resolved | |
Milestone | |
Patch | No |
http://supervisord.org/manual/current/api.process-control.html#api.process-control.supervisor-sendremotecommevent
http://supervisord.org/manual/current/events.html#event_listeners_and_event_notifications
http://fallenpegasus.livejournal.com/852077.html
http://robey.livejournal.com/53832.html
http://github.com/nkallen/cache-money/tree/master
https://launchpad.net/gearman-php-ext
http://www.scribd.com/doc/6134982/Starling-Workling-Simple-Distributed-Background-Jobs-With-Twitters-Queuing-System-Presentation
and these for potential job backends:
http://github.com/starling/starling
http://rubypond.com/articles/2008/07/17/the-complete-guide-to-setting-up-starling/
- client can lock a queue task for a set period of time while processing it
- if a lock expires, other queue clients can pick up the task
- clients can delete tasks when they're done
http://www.danga.com/gearman/
Milestone ⇒
State ⇒ Assigned
Patch ⇒ No
Assigned to Chuck Hagenbuch
Queue ⇒ Horde Framework Packages
Summary ⇒ Horde_Queue
Type ⇒ Enhancement
Priority ⇒ 1. Low
doing them in-line. have api calls for picking up object updates
(listeners essentially). also have api calls for whether an app does
update triggers for a given content-type.
default backend - Horde_Queue_Unqueue (or immediate?) that processes
tasks immediately upon being added to the queue. Not great for
performance, but no worse than the current inline tasks, and provides
an easy path for small sites that don't need to set up a queue daemon.
sql backend along with SQS
monitor the daemon with supervisord?
http://q4m.31tools.com/