From: Tony Arcieri <tony@...>
Date: 2007-09-26T13:30:44+09:00
Subject: Fibers

------=_Part_27732_33362903.1190781044077
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Let me say first, fibers are a great feature and I'm really glad to see
them.  I think they have enormous potential.

I experimented with them by writing a simple actor model
implementation<http://pastie.caboo.se/97050>.
I noticed a couple of things:

In a subclass of Fiber, it seems initialize is never called.

I believe if it would be immensely useful if you could somehow specify the
execution time for a fiber.  By that I mean that after calling Fiber#resume
the resumed fiber would automatically Fiber#yield after X amount of time
(unless it calls Fiber#yield before that).  This would be useful for
providing a simple preemption mechanism for scheduling the execution of
multiple fibers.

Is there any way to do that?

Tony Arcieri

------=_Part_27732_33362903.1190781044077
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Let me say first, fibers are a great feature and I&#39;m really glad to see them.&nbsp; I think they have enormous potential.<br><br>I experimented with them by writing a <a href="http://pastie.caboo.se/97050">simple actor model implementation
</a>.&nbsp; I noticed a couple of things:<br><br>In a subclass of Fiber, it seems initialize is never called.<br><br>I believe if it would be immensely useful if you could somehow specify the execution time for a fiber.&nbsp; By that I mean that after calling Fiber#resume the resumed fiber would automatically Fiber#yield after X amount of time (unless it calls Fiber#yield before that).&nbsp; This would be useful for providing a simple preemption mechanism for scheduling the execution of multiple fibers.
<br><br>Is there any way to do that?<br><br>Tony Arcieri<br>

------=_Part_27732_33362903.1190781044077--