Giovanni Piero Deretta wrote:
On Tue, Nov 4, 2008 at 9:35 PM, Alexander Terekhov <terekhov@web.de> wrote:
k-oli@gmx.de wrote:
[... fibers ...]
I'm open for discussion.
First define 'fibers' in common sense language. This is a request for discussion to all. :-)
Here goes a shot at a definition: A fiber is a coperatively scheduled [purely/mostly userspace] thread of execution. AKA (symmetric) coroutines, green threads, co-threads, user contextes, etc.
"A fiber is a unit of execution that must be manually scheduled by the application [do you really want and/or capable of that?]. Fibers run in the context of the threads that schedule them [correct]. Each thread can schedule multiple fibers [correct]. In general, fibers do not provide advantages over a well-designed multithreaded application [that's right]. However, using fibers can make it easier to port applications that were designed to schedule their own threads [i.e. archaic academic coroutines apps]." Welcome back to the past. http://msdn.microsoft.com/en-us/library/ms682661(VS.85).aspx :-) regards, alexander.