From: "Geo" 

Nope. Not for resolving the dns names which is what takes so much time.

Geo.

"Ellen K."  wrote in message
news:89b611h4bts4p57qfcopdqppshn2lhejm2{at}4ax.com...
> ?  Doesn't each one have to wait for the previous one?
>
> On Tue, 15 Feb 2005 23:14:57 -0500, "Geo"
 wrote in
> message :
>
> >"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