On Jun 6, 2006, at 6:08 PM, Chih-Chao Lam wrote:
> First off, Ezra, thank you for putting out BackgrounDrb. Looks like
> a very useful framework.
>
> I have a newbie question about ruby threads. Are there any general
> things to avoid doing when using ruby threads and rails?
>
> Also specifically, will using BackgrounDrb avoid the socket problem
> described in this link (extracted from Rails wiki):
> http://clipclip.org/chao/clips/detail/6216/howtosworkerthreads-in-
> ruby-on-rails
>
> I''m hoping it will because, presumably, BackgrounDrb runs in a
> separate process from the actual rails web app?
>
> Thanks,
> chao lam
> _______________________________________________
> Backgroundrb-devel mailing list
> Backgroundrb-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/backgroundrb-devel
You''re welcome, thanks for the kind words! And you are correct, your
worker classes run in a separate ruby interpreter in its own separate
process. But currently all your workers run in threads in the same
process so you have to be mindful. I think you should be fine doing
what you want with sockets. And if you end up running into issues, I
am working on an addition that will allow your workers to spawn their
own slave child processes. So stay tuned. And post back here if you
run into any issues.
Cheers-
-Ezra
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20060606/cf967077/attachment-0001.htm