Hi Aaron, Have you looked at beanstalkd? It seems to have its own protocol that fits the bill fairly well.
Cheers, Mike On Thu, Nov 6, 2008 at 2:51 PM, Aaron Stone <[EMAIL PROTECTED]> wrote: > > Hi Folks, > > I've been lately about message queues, and noticing there are a > projects out there that speak memcache protocol for queues. Most of > them work by polling, though, and that sucks, and most seems to > overload the meaning of GET, all in different ways. > > I'm imagining a generic set of protocol elements that define the > messaging in the memcache binary protocol that allow the various > memcache queue projects to speak the same language with the same (or > reasonable similar) semantics. I'd also like to define commands that > block on the server, so the client can say something like, "Send me > the next item in one of the following queues whenever you're ready, > meanwhile I'll be sleeping, thanks". > > Queues I've seen: > MemcacheQ: http://memcachedb.org/memcacheq/ > Starling: http://rubyforge.org/projects/starling/ > Native hack: > http://broddlit.wordpress.com/2008/04/09/memcached-as-simple-message-queue/ > Depcached: http://www.marcworrell.com/article-2287-en.html > Sparrow: http://code.google.com/p/sparrow/ > > My first goal right now is to write up a comparison of how each of > these projects is using the memcache protocol elements (i.e. what is > the meaning of GET/SET on a queue? Are there new commands like QUEUE > and DEQUEUE? etc.) and see if there's enough common ground to get > moving. > > Does anybody on the list have negative / positive experiences with any > of the queue implementations? Does anybody know of additional > implementations I should look at? > > Aaron >
