Backgroundrb devel - Aug 2008 - Persistent worker scheduled_at

Hemant would you be interested in a patch adding an
''scheduled_at'' attribute
to BdrbJobQueue objects? I''m considering the best way to run quick,
asynchronous scheduled events targeting future events. Is this an
appropriate use of the persistent worker queue mechanism or is there a
better method already built in or do you have a better idea of how to
implement something like this?

- P Baker
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080819/cfcb9f17/attachment.html>

Persistent workers will be best for this and yes, i will be interested
in the patch (just don''t forget to write testcases for it, in past,
not having test cases, was a big problem, i don''t want to go that
memory lane again).



On Tue, Aug 19, 2008 at 7:53 PM, P Baker <me at retrodict.com>
wrote:
> Hemant would you be interested in a patch adding an
''scheduled_at'' attribute
> to BdrbJobQueue objects? I''m considering the best way to run
quick,
> asynchronous scheduled events targeting future events. Is this an
> appropriate use of the persistent worker queue mechanism or is there a
> better method already built in or do you have a better idea of how to
> implement something like this?
>
> - P Baker
>
> _______________________________________________
> 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

P Baker wrote:
> Hemant would you be interested in a patch adding an
''scheduled_at''
> attribute to BdrbJobQueue objects? I''m considering the best way to
run
> quick, asynchronous scheduled events targeting future events. Is this 
> an appropriate use of the persistent worker queue mechanism or is 
> there a better method already built in or do you have a better idea of 
> how to implement something like this?
"me to".  I would be interested in this functionality...

Cheers

Ed W