On Jun 23, Jim Sproull wrote:
> This all works fine. However, the get_sessionid and set_sessionid are
> using a dbm file, which is locked and unlocked during each request. (I
> know, I know). Obviously, this is a lot more load that is necessary. I
> tried using a simple global variable (defined before the handler), but this
> was unreliable as it was set differently for each request. No doubt due to
> different processes handling each request. Can anyone suggest a better way
> of handling this globablly accessed data? Thanks.
If you search the new-httpd list, you should be able to find a
patch I posted to mod_usertrack (quite some time ago) that in
addition to adding a configuration option (to set the cookie's
domain or something like that), makes mod_usertrack create two
additional notes -- "out-cookie" and "in-cookie" which are set to
the value of its session cookie depending on whether it is outgoing
(being set) or incoming (subsequent requests).
With that, it is very easy to know when the cookie is new, and if
you log the two fields seperately, you can easily calculate the
number of your visitors who have cookies disabled (or only make
a single request to the webserver).
Jim
