Another option is to use activemessaging - like backgrounDRb it lets you
things asynchronously so your controller can return, but rather than a
process model, it is a messaging model.
I know several people using this for doing email notifications
me) - e.g. some event occurs, controller pushes a message on a queue,
processor asynchronously pops off this message and spends whatever time
necessary to handle it and send out a bunch of emails to ‘subscribers’.
On 6/26/07, Josh email@example.com wrote:
used. it seems that the user is having to wait for rails to send the
If the email is huge, you might use BackgrounDRb to handle the process.