From: Ellen K. 

You said it in ProgrammerSpeak.   :)

On Wed, 16 Feb 2005 14:11:59 -0000, "Paul Ranson"
 wrote in message :

>That would be event driven from the network transport, no point in
>fiberising it.
>
>Paul
>
>"Geo"  wrote in message
news:4212c955$1{at}w3.nls.net...
>> "Paul Ranson"  wrote in message
>> news:4211fab9{at}w3.nls.net...
>>
>>> But fibers came after threads, so fibers are generally only
used when the
>>> application can benefit from doing its own scheduling. A search for
>>> fiber,
>>> sqlserver and msdn should turn up a couple of interesting articles.
>>
>> I know the perfect usage for fibers, it could be used to create a really
>> fast traceroute program. One thread to do the traceroute but multiple
>> fibers
>> each resolving a single node along the route. Because each has to wait for
>> input, the app thread should do the scheduling based on demand.
>>
>> Have I got the idea of your scheduling comment?
>>
>> Geo.
>>
>>
>

--- BBBS/NT v4.01 Flag-5