Hello all, i just started using backgroundrb and i really like it a lot so far. I finally succeeded in setting up version 0.21 and the examples from the readme run fine. Now i do not want to create and delete my worker anytime i want it to do something but call repeatedly a method with arguments. There is a arg_method defined in the readme so i guess this is a feasible way to procede. Unfortunatly i could not find the syntax to pass args to such a method. I hope this is not too stupid a question and you excuse my BASE. Also i would like to know how to determine the version of backgroundrb. I found it rather irritating to come across a lot of outdated documentation and it took me a while to understand that my rubyforge install was outdated. Maybe you could consider writing a version string in backgroundrb.log ? regards tom -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20061201/4ce42629/attachment.html
* tom roth (rawdlite at googlemail.com) [061201 10:33]:> Hello all, > > i just started using backgroundrb and i really like it a lot so far. > I finally succeeded in setting up version 0.21 and the examples from the > readme run fine. > Now i do not want to create and delete my worker anytime i want it to do > something but call repeatedly a method with arguments. > There is a arg_method defined in the readme so i guess this is a feasible > way to procede. > Unfortunatly i could not find the syntax to pass args to such a method. > I hope this is not too stupid a question and you excuse my BASE.for worker methods you define yourself, there is no special syntax, you would define it as you would with any ruby method. If you are using the scheduler for periodic execution, you just have to make sure that the arguments matches the one in the method definition. /skaar> Also i would like to know how to determine the version of backgroundrb. I > found it rather irritating to come across a lot of outdated documentation > and it took me a while to understand that my rubyforge install was > outdated. Maybe you could consider writing a version string in > backgroundrb.log ?If you add this to trac, I''ll add this to the next release. If you really want to know the version right now, you can issue: > BackgrounDRb::VERSION in the console. /skaar -- ---------------------------------------------------------------------- |\|\ where in the | s_u_b_s_t_r_u_c_t_i_o_n | | >=========== W.A.S.T.E. | genarratologies |/|/ (_) is the wisdom | skaar at waste.org ----------------------------------------------------------------------
On 01/12/06, skaar <skaar at waste.org> wrote:> > > > for worker methods you define yourself, there is no special syntax, you > would define it as you would with any ruby method.Thanks a lot, this helped me. Actualy i had already tried it, but my worker was not running and i got confused by the error message. So this leads me to the next question: What is the best way to determine whether a worker for a given job_key is running ? If you are using the scheduler for periodic execution, you just have to> make sure that the arguments matches the one in the method definition. > > /skaar > > > Also i would like to know how to determine the version of > backgroundrb. I > > found it rather irritating to come across a lot of outdated > documentation > > and it took me a while to understand that my rubyforge install was > > outdated. Maybe you could consider writing a version string in > > backgroundrb.log ? > > If you add this to trac, I''ll add this to the next release. If you > really want to know the version right now, you can issue: > > > BackgrounDRb::VERSION > > in the console.cool, i added it to trac then. regards tom /skaar> > -- > ---------------------------------------------------------------------- > |\|\ where in the | s_u_b_s_t_r_u_c_t_i_o_n > | | >=========== W.A.S.T.E. | genarratologies > |/|/ (_) is the wisdom | skaar at waste.org > ---------------------------------------------------------------------- >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20061202/e364a3a2/attachment.html
Reasonably Related Threads
- BackgrounDRb 0.2.0 Release! Complete rewrite.
- New Backgroundrb Speed Issues?
- backgroundrb launches concurrent instances of same job
- rails 1.2.1, locomotive and backgroundrb
- Passing object into results - "can''t convert DRb::DRbUnknown into Hash - (TypeError)"