Re: thread safety

In my case, I have a windows DLL which uses libwww underneath to POST and 
get responses back from a servlet. This windows DLL when used by clients, 
who send quick successive requests, results in a failure.

The first request *hangs* so to speak where as the second one, does succeed. 
I noticed that in this case, I get a Host info... REUSING CHANNEL 022310A0 
status message. I tried to mimic the above behaviour through an independent 
threaded NT VC++ application and got the same behaviour.

My main consideration is to get around my DLL problem.

-Tanmay

-----------------------
Tanmay Patwardhan
Applications Developer,
UBS Warburg,
Chicago, IL.
-----------------------





>From: Richard Atterer <richard@list03.atterer.net>
>To: www-lib@w3.org
>Subject: Re: thread safety
>Date: Thu, 1 May 2003 01:47:13 +0200
>
>
>On Wed, Apr 30, 2003 at 05:29:12PM -0500, Tanmay Patwardhan wrote:
> > I did read previous discussions on the list about libwww not being 
>thread
> > safe. From my usage of posting a request and getting large data back, on
> > Solaris, multithreading *seems* to work fine. But it fails miserably on
> > NT.  Has anyone lately given a thought, worked on multithreaded usage of
> > the libary?
>
>Why would you *want* it to be thread-safe? It can do several downloads
>simultaneously in a single thread, so what benefits does running it in
>several threads have?
>
>Cheers,
>
>   Richard
>
>--
>   __   _
>   |_) /|  Richard Atterer     |  CS student at the Technische  |  GnuPG 
>key:
>   | \/¯|  http://atterer.net  |  Universität München, Germany  |  
>0x888354F7
>   ¯ '` ¯
>


_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*  
http://join.msn.com/?page=features/junkmail