> backgroundrb is not just a scheduler, it's a way to delegate heavy/
That is why I called it a fancy scheduler.
What are you calling "fancy scheduler" is just a part of backgroundrb
and it is not that part that we talking about.
> response from server. Forking child process to work on video and
> continuing execution (ie show "please, wait" page, checking for
> delegated task completion) makes user experience much more pleasant.
Add the requested task to a queue (directory, table, etc). Have a cron
task run on-demand/periodically reading from the queue and processing
the request. When the cron job has finished a task have it notify the
web server (update a table, move the file out of the directory, etc)
How would you raise an exception? How would you spec/test such
implementation, keeping in mind that "table updated" or "file moved"
is certainly not equal to "scheduled task successfully completed".
Trying to answer these questions wouldn't you end up reinventing some
limited and, likely, unstable bicycle, already invented and called