Gregory (Grisha) Trubetskoy wrote:
Yeah, we've got to be inline with the HTTP Project - prefork is the
default on unix systems, so we have to abide by it...
So I guess the solution is that we need to reserve two locks instead of
just one?
It seems a shame to waste locks if they are not goi
On Fri, 24 Jun 2005, Jim Gallacher wrote:
Gregory (Grisha) Trubetskoy wrote:
Yeah, we've got to be inline with the HTTP Project - prefork is the
default on unix systems, so we have to abide by it...
So I guess the solution is that we need to reserve two locks instead of
just one?
It se
Nicolas Lehuen wrote:
Is there a way to forbid PythonSessionOption from appearing in a
.htaccess file ? If not, then there is no advantage (security-wise) in
having a different configuration directive.
I know we've decided on using PythonOption session_* instead, but
looking at http://www.apa
I think the way to go is PythonOption now, then consider
PythonSessionOption later - I too do not like too many options and am not
sure that session handling is a core function.
Changing it later (if we decide to) should not be a big problem - it's
pretty easy to just spit our a wrning that
