On Nov 3, 2:29 pm, Dustin <[email protected]> wrote: > I wrote this a long time ago and it still makes sense to me: > > http://www.rockstarprogrammer.org/post/2008/oct/04/what-matters-async...
Very interesting, thanks! I actually already had read and bookmarked it back in February[1], but forgot! You pointed out that both Starling and MemcacheQ require clients to poll the servers for new jobs. Interestingly, Kestrel supports "blocking fetch"[2]. The other problems — "neither has positive job completion acknowledgments, crash handling, priorities, delays, or any room for them" — definitely make sense to me and probably still apply to Starling and Kestrel. Thanks! [1] http://delicious.com/avi4now/queue [2] http://wiki.github.com/robey/kestrel/blocking-fetch --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/beanstalk-talk?hl=en -~----------~----~----~----~------~----~------~--~---
