On Tue, Sep 23, 2008 at 4:00 AM, Dustin <[EMAIL PROTECTED]> wrote: > > > On Sep 22, 11:25 am, mark <[EMAIL PROTECTED]> wrote: > >> this is the best of all the open-source queuing solution ever!!!! >> simple, fast and rocks out loud!!! > > Which ones have you tried, and what did you not like about them? > > memcached has several properties that I think make it quite poorly > suited as a platform for building a job queue.
You mean the non-blocked I/O model? What properties that make it quite poorly? Can you give us a bit more detail? > You can certainly work > around them, but if the goal is to get it to work with existing > memcached clients, then you've recreated starling (including the part > where it forces the clients to poll for jobs, which will cause you to > try to balance between pickup latency and massive CPU utilization on > both server and client). > > If it's stateless, then you also have to have semantics for jobs > that get dropped by clients. e.g. if I ask for a job and then > immediately crash, does the job get run? Yes, this is a problem we should solve. Maybe a visible timeout and explicit delete will make this done, but also a bit more complicated to end users. > > Of course, I'm not trying to suggest there shouldn't be innovation > in this space, but there are a *lot* of options, and I don't > understand what the others are lacking (I've used and written several > myself). > -- Steve Chu http://stvchu.org
