Hi Felix,
MiddleMan.new_worker returns the worker''s key. For example, if you use
w = MiddleMan.new_worker(:worker => :my_worker, :worker_key =>
''1'')
#the value of w is 1
To access the worker, you use
MiddleMan.worker(:my_worker, ''1'').some_method_call_here.
If you don''t pass in a worker_key, then you receive nil.
That''s my understanding.
Jonathan
On Mon, Feb 16, 2009 at 3:54 PM, Felix Holmgren <felix.holmgren at
gmail.com>wrote:
> I''ve been checking out all the async gems and plugins for Rails,
and
> decided to give BackgroundRb a shot. Unfortunately, I''ve not even
been
> able to get past the initial stages.
>
> Whenever I call MiddleMan.new_worker, it invariably returns nil. The
> log file remains empty.
>
> I''ve only tried this from the console so far. If I can''t
even do this
> successfully, I''m in no mood to try to start to write code,
>
> I''ve followed the example instructions to the letter, and
confirmed
> that the BGRB server is running, as well as my Mongrel. I''m
running on
> Leopard.
>
> Rails 2.2.2
> ruby 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0]
>
> I''d really appreciate it if someone could give me some feedback on
> this fast. Otherwise I''ll have to drop BackgroundRb and go with a
> hand-made, simpler scheme for now, as the deadline for my project is
> very close (basically, like NOW).
>
> Many thanks!
> _______________________________________________
> Backgroundrb-devel mailing list
> Backgroundrb-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/backgroundrb-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20090216/33e3e5dd/attachment.html>