Backgroundrb devel - Apr 2008 - Lingering status?

Is it expected that MiddleMan.ask_stats will return a status for a worker
that has been MiddleMan.delete_worker''ed?  The worker isn''t
showing up in
MiddleMan.query_all_workers, so it seems that is shouldn''t have a
status
either.

Is there a way to define a callback that is called at deletion, to reset the
status, or do I need to write my own method to reset the status before I
delete the worker?

TIA
-todd[1]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080408/acb1ae5f/attachment-0001.html

yes worker status keeps lingering even after a worker has been
deleted. You can search mailing list archives on how to write a custom
handler which will handle delete request and let you attach custom
handlers.

On 4/8/08, Todd Willey <todd at rubidine.com>
wrote:
> Is it expected that MiddleMan.ask_stats will return a status for a worker
> that has been MiddleMan.delete_worker''ed?  The worker
isn''t showing up in
> MiddleMan.query_all_workers, so it seems that is shouldn''t have a
status
> either.
>
> Is there a way to define a callback that is called at deletion, to reset
the
> status, or do I need to write my own method to reset the status before I
> delete the worker?
>
> TIA
> -todd[1]
>
> _______________________________________________
>  Backgroundrb-devel mailing list
>  Backgroundrb-devel at rubyforge.org
>  http://rubyforge.org/mailman/listinfo/backgroundrb-devel
>

-- 
Let them talk of their oriental summer climes of everlasting
conservatories; give me the privilege of making my own summer with my
own coals.

http://gnufied.org