The EM based client is good if you're working with multiple beanstalk connections within the same process. If you have your queue on a different server and you're finding that IO from the queue is holding you up from getting things done. EM lets you do asynchronous IO. That way you can kick off multiple pulls from the queue and work once the job has been returned.
If you're grabbing off a queue on the same box and you're not using any of the other EM features, there's really no advantage to using an EV based client since IO shouldn't be blocking you. To begin with I'd say you're probably better off just using the beanstalk-client gem. At least those are my thoughts on it. Paul On Sat, Aug 15, 2009 at 3:31 PM, Tom<[email protected]> wrote: > > Hi, > > anybody got some experience in using beanstalk with ruby via either > the standard gem 'beanstalk-client' or the 'Jack' gem (http:// > github.com/dj2/jack/tree/master) The latter is based on EventMachine > and seems to be newer. > Being based on EV is sold as an advantage, but I don't know EV enough > to understand what this really brings to the table. > > Any first hand experience/ideas which gem is better? > > Thanks > > Tom > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
