Displaying 5 results from an estimated 5 matches for "worker_status".
2007 Dec 19
6
thread_pooling sleeping
I''m trying to run a single worker that could perform a periodic task
for a given user.
>From a controller, I imagine something like:
def start_job
MiddleMan.ask_work(:worker => :foo_worker, :worker_method => :perform_task,
:data => { :user_id = current_user.id })
end
def check_job
@status = MiddleMan.ask_status(:worker => :foo_worker)[current_user.id]
end
2008 May 09
1
register_status for excess thread_pool?
...def makepdf(user)
txt = user.to_s + " started"
save_status(user, :progress, txt)
do_report(user)
txt = user.to_s + " ended"
save_status(user, :progress, txt)
end
def save_status(user_id,key,data)
@status_mutex.synchronize do
@worker_status[user_id] = { :key => key, :data => data}
end
register_status(@worker_status)
end
However, if more than 10 requests are submitted to the worker
at a time, those in excess of 10 are queued and thus never
get assigned a status in register_status. So, in my Rails/ajax
view, I have no...
2008 Jan 18
8
Query All Worker
What does the method query_all_workers() do? There is no documentation
on what this method returns (1.0.1 version).
Orion
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080118/9f9b8112/attachment.html
2007 Nov 14
7
BackgrounDRb version 1.0RC1 available now
...backs.
=== Exciting new stuff
* Rock solid stable ( or will be , after few bug reports )
* Master Process is using a hash for storing status of each worker.
I am thinking of adding something like this:
#backgroundrb.yml
status_storage:
storage: db
database: worker_status
Above code would fullfill thy wishes of persitent worker status
storage. Any more ideas, welcome.
* Each worker comes with Event loop of its own and can potentially
do lots of fancy stuff. Two noteworthy methods are:
connect(ip,port,Handler)
start_worker(ip,port,Handler)...
2007 Dec 17
7
Get "some read error" on calls to worker
I''m running the latest from svn (rev 285). I''ve been having a problem
launching a process repeatedly. What happens is that I get a debug
message "some read error" and then the worker refuses to run again.
I''ve stripped my worker down to just doing a puts and it still happens.
Like the other threads I want to launch my workers as needed, however I
get the