[Backgroundrb-devel] Backgroundrb alternative idea
reynard.list at gmail.com
Fri Nov 9 10:08:33 EST 2007
I was just thinking if this simple idea would serve to replace backgroundrb:
What if the worker is replaced with just a ruby script (can be
anything actually: php, perl, etc)
Rails application can just spawn new process by calling this worker
script (passing data, and possibly uniq id)
The worker script then store the result in database keyed by the uniq
id (which is accessible by the Rails app), So the Rails app can check
on the result by querying the database.
Isn't that exactly what backgroundrb does?
I would love to get comments / suggestions.
More information about the Backgroundrb-devel