Rupert Galea
2008-Jan-29 21:19 UTC
[Backgroundrb-devel] Does status disappear after worker exits?
Hemant, From http://backgroundrb.rubyforge.org/ "Currently, when a worker is deleted/exits, its result/status is also gone (i.e. you can?t query the status of a worker which is not running). This behaviour is expected to change in future releases." Is this still true? I ask because I am checking for a status after a worker exits and the code seems to work. Thanks Rupert
hemant
2008-Jan-30 05:19 UTC
[Backgroundrb-devel] Does status disappear after worker exits?
On Wed, Jan 30, 2008 at 2:49 AM, Rupert Galea <rupert at adverplex.com> wrote:> Hemant, > > From > http://backgroundrb.rubyforge.org/ > > "Currently, when a worker is deleted/exits, its result/status is also > gone (i.e. you can''t query the status of a worker which is not > running). This behaviour is expected to change in future releases." > > Is this still true? I ask because I am checking for a status after a > worker exits and the code seems to work.No that has been changed and status/result objects remain even after a worker has died -- 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
Apparently Analagous Threads
- Workers without rails environment
- Get "some read error" on calls to worker
- Query All Worker
- [PATCH] x 2 - Fix for "null pointer exception" when ask_status is called before worker is run, and docfixes
- Backgroundrb 1.0.1: uninitialized constant Packet::ClassHelpers (NameError)