----- Original Message ----- From: "Alexander Terekhov" <terekhov@web.de> To: <boost@lists.boost.org> Sent: Tuesday, November 04, 2008 11:12 PM Subject: Re: [boost] [threadpool] new version - fork/join (recursive/fibers)
Giovanni Piero Deretta wrote:
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. :-)
What do you have counter "archaic academic coroutines apps"? Is it for archaic, for academic or for corutines? ;-) Vicente