Hi there. I'm new to beanstalkd and was hoping it would do what I'm
wanting, but I'm not sure if it's suited for my need. I've got a
Rails app with a form such that a user can upload an image. I want to
do processing on that image in the background with some separate Perl
script. What I want is to be able to start the processing by calling
system('my command') or just `my command`, and let that happen in the
background so the user doesn't have to potentially wait around a long
time while the processing takes place. I'd like to be able to capture
any error messages from the background process. Some processes can
only be run one at a time, so if one is already running, I want to add
new requests to a queue and later process them.
The tutorials I've seen for beanstalkd all involve message passing.
I'd like to be able to do something like beanstalk.system('my
command') and get back a process ID for the forked process. I was
using Spawn (http://github.com/thoughtbot/spawn/tree/master) but
thought beanstalkd might be more suited to my needs because I don't
need extra instances of ActiveRecord created.
Is beanstalkd intended for this type of usage? If so, could someone
write up some sample code for running system commands asynchronously?
I would also appreciate links to relevant tutorials and an API so I
can know a description of the methods and classes available in
beanstalkd. Thanks!
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
