[8686] in www-talk@info.cern.ch
Re: Session-Id
daemon@ATHENA.MIT.EDU (John Franks)
Fri Jul 21 22:08:09 1995
Date: Fri, 21 Jul 1995 21:06:16 -0500
From: John Franks <john@math.nwu.edu>
To: pitkow@cc.gatech.edu, www-talk@w3.org
In-Reply-To: <199507212304.TAA23595@hapeville.cc.gatech.edu>
Resent-From: www-talk@w3.org
In article <199507212304.TAA23595@hapeville.cc.gatech.edu> James Pitkow writes:
>
>Further more, the generation of unique ids on the server side means
>that some shared memory is used, which means locking, which means
>blocking. This can only serve to decrease the throughput of servers
>(what's the point of issuing unique ids if you turn away half of the users
>away?). Additional resources (computational and memory) are consumed
>by the management of ids and their recycling.
>
No, for a preforked server each preforked process uses its id plus a counter
which it increments for each request. For a threaded or forking server there
is only one counter which is incremented before forking.
>If a client generates an id, the server simply logs this to file
which means locking, which means blocking... ;)
--
John Franks Dept of Math. Northwestern University
john@math.nwu.edu
