On Sep 11, 9:50 am, "Dominic Sisneros" <[EMAIL PROTECTED]> wrote:
> The fibers are coroutines so when it yields it gives up control to whichever
> routine resumed it. Using a fiber pool is quicker and uses less memory than
> a thread
> pool.http://oldmoe.blogspot.com/2008/08/ruby-fibers-vs-ruby-threads.html
But if the Fiber is blocked, it can't yield. In the comments of the
same article oldmoe states Fibers are not pre-emptive.
So green-threads without a scheduler and manual flow-control? Meh.
-Sam
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"DataMapper" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/datamapper?hl=en
-~----------~----~----~----~------~----~------~--~---
