- From: <jose.kahan@w3.org>
- Date: Fri, 1 Sep 2000 14:30:26 +0200 (MET DST)
- To: jose.kahan@w3.org
- CC: Mihut Ionescu <mihut@EECS.Berkeley.EDU>, www-lib@w3.org
As a followup, Jens had proposed an alternate method that may work right. I don't see any problem, except for the cache (which isn't shared). Each thread should have its own cache directory. http://lists.w3.org/Archives/Public/www-lib/2000JulSep/0166.html In our previous episode, jose.kahan@w3.org said: > Hello, > > In our previous episode, Mihut Ionescu said: > > > > I would like to build a multithreaded proxy using libwww. Each thread > > would handle a different connection, where true pipelined requests can be > > serviced (multiple requests can be received over this connection before > > any response is sent back). > > Maybe the question is "is libwww multi-thread safe?". > > My answer is that I don't think it's 100 %safe. There are some places > with global static variables, the authentication trees are not semaphore > protected, and so on.
Received on Friday, 1 September 2000 08:30:34 UTC