httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From r..@ai.mit.edu (Robert S. Thau)
Subject Re: vote status
Date Thu, 15 Feb 1996 21:51:16 GMT
  HTTP is stateless, the server is not. It's entirely conceivable that 
  someone may want to write a module that logs the way peristent 
  connections are used, or that a future version of the HTTP protocol (for 
  example, Alex Hopmann's session extension draft) will involve the use of 
  data from previous connections.

This could be addressed by distinguishing the *per-connection* resource
pool from the *per-request* resource pool (making the latter a sub-pool
of the former of course).  In particular, the case you mention (preserving
headers across requests) could be handled by copying the headers named as
being persistent to a table associated with the per-connection pool (which
would stay around even after the first request read in off the persistent
connection were processed and its own associated resource pool cleared).

rst

Mime
View raw message