From: Christopher Dicely <cmdicely@...>
Date: 2009-10-16T00:18:32+09:00
Subject: Re: Problems With Fibers in Threads

On Wed, Oct 14, 2009 at 12:13 PM, Chris Wailes <chris.wailes@gmail.com> wrote:
> OK, that does appear to be the problem as the Fibers are created in
> various threads then executed by a thread from the thread pool.  Is the
> inability to call a fiber across different threads a 'feature', or
> simply a consequence of implementation?  Is this going to remain the
> situation in the future?  Is there a way around it?  Where is this
> behavior mentioned?

It seems pretty fundamental. You might be able to work around it by
using Procs to store the jobs but then having the thread that runs
each Proc create a Fiber to run the Proc when it is run (I haven't
tested it, but it seems like it should work.) Its not mentioned in the
documentation for Fiber (though it should be), but it is mentioned on
page 186 of the most recent edition of the Pickaxe (_Programming Ruby
1.9: The Pragmatic Programmers' Guide_, by Dave Thomas.)