W3C home > Mailing lists > Public > www-talk@w3.org > July to August 1995

Re: Session-Id

From: James Pitkow <pitkow@cc.gatech.edu>
Date: Fri, 21 Jul 1995 22:28:17 -0400 (EDT)
Message-Id: <199507220228.WAA24236@hapeville.cc.gatech.edu>
To: john@math.nwu.edu (John Franks)
Cc: pitkow@cc.gatech.edu, www-talk@w3.org


John Frank wites:

> 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.

The former scheme does not ensure unique ids, which is the goal. PIDs are 
assigned sequentially, so you'd be in trouble within your first 5 requests.
Most servers are no longer forking per request.

>If a client generates an id, the server simply logs this to file
> which means locking, which means blocking...  ;)

Clients have infinitely more cycles to spare than servers.  Besides,
I've never seen a client do 100 requests per second, which is the
magnitude where locking becomes an issue.

Received on Friday, 21 July 1995 22:28:23 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:32:57 UTC