Displaying 3 results from an estimated 3 matches for "backgroundbr".
Did you mean:
background
2007 Dec 17
1
Some more updates, enhancements and fixes
...e of days. Here is a brief list:
1. Results from worker stays even after a worker dies.
2. You can ask backgroundrb to store status objects in memcache
cluster now. by default its stored in master process memory, but I
have introduced an option to allow it to be stored in a memcache
cluster:
#backgroundbr.yml
:result_storage:
:memcache: "10.10.10.2.11211,10.10.10.6:11211"
3. Check for Ruby version.
4. Introduced Thread pool now, all the workers have access to
"thread_pool" object, which can be used to run concurrent tasks in
ruby threads:
An example,...
2008 Jan 09
0
BackgrounDRb 1.0.1 release available now
...turn status
objects set by you in worker code)
* Removed messing around with Core classes. BackgrounDRb doesn''t
change behavior of any core classes now.
* Worker status objects stay even after a worker dies.
* BackgrounDRb can now store worker results/status objects in Memcache now.
#backgroundbr.yml
:result_storage:
:memcache: "10.10.10.2.11211,10.10.10.6:11211"
* Fixed issues with thread pool.
* Committed Patches by Jason for test helper.
* Committed patch for honoring wday option by Adam.
News:
* Advanced Rails Recipes book contains a full recipe on using
Ba...
2007 Apr 08
3
Updater and PeriodicUpdater fighting with one another
I have a long-running process to build a directory tree in a database
from a very large and deep folder structure. I am using sessions for
security, but the process takes so long that it never finishes.
Having tried and failed to override the session time-out, I am trying
to work around the problem by having a PeriodicUpdater tickle the
session by loading a page every minute. But I am also