RE: apache style squid?

--MimeMultipartBoundary
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

From: Michael O'Reilly
Sent: 09 October 1997 09:04
To: Andres Kroonmaa
Cc: squid-dev@nlanr.net
Subject: Re: apache style squid?

I think you're still missing the point. It's not that only one thread
can write, but for any one variable, at any one point in there, this
is a only a single thread that could possibly write to the
variable. This is fairly easy to setup.

Also don't forget one of the classic thread problems. With multiple
readers and writers, if you have lots of readers (as very busy caches
would), then there may not be a point at which the number of readers
has returned to 0 and the writer can come in. So you should give
priority to writers at all points.

I say this because Solaris threads has rwlock's which automatically
behave in this way but (I believe) pthreads doesn't, and you have to
do it yourself, and any thread implementation would be in pthreads,
not Solaris (i.e. Unix international) threads.

Jonathan L.

Origin, 323 Cambridge Science Park,Cambridge,UK. Tel:+44 (1223)
423355
 ---[ It is impossible to enjoy idling thoroughly unless one has ]---
 ------------[ plenty of work to do - Jerome K. Jerome ]-------------
Fight spam! http://spam.abuse.net/ These opinions are al
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.0
Charset: noconv

iQA/AwUBNDzf84YLUv2rigzBEQJ1bACggJhvbRHHXNUylUdLT4HIopOCUXQAnjaV
mGUO3HbZcsUQ8AdfU2yiaX8s
=5e2/
-----END PGP SIGNATURE-----

--MimeMultipartBoundary--
Received on Tue Jul 29 2003 - 13:15:43 MDT