Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (nike.apache.org: domain of support@bettercgi.com
 designates 216.17.105.202 as permitted sender)
Date: Mon, 29 Nov 2010 10:19:34 -0600
From: Ray Morris <support@bettercgi.com>
Subject: Re: Apache log modules
To: modules-dev@httpd.apache.org
In-Reply-To: <20101129025152.GA27782@seid-online.de> (from rm@tuxteam.de on
	Sun Nov 28 20:51:52 2010)
Message-Id: <1291047574.1076.30@raydesk1.bettercgi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; DelSp=Yes; Format=Flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> > My assumption is that both client and server have KeepAlive enabled.
> > In that case, should there "generally" not be just one connection
> > only?
>=20
> This assumption is most likely wrong. Even with keep-alive browsers =20
> will
> open more than one connection. After all, keep-alive and multi-connect
> solve different problems.

    Indeed in MOST cases there will be several connections - IE and
Firefox open multiple connections.  Without knowing the actual purpose,
the problem you're trying to solve, the best course may be a module
which logs and increments a cookie, combined with sorting by IP + time.
One could also say that anything with a mime type of text/html and a
status code other than 302 is a page, with mime types like image/*
being elements of that page coming from the same click.  That's how
we organize a certain report - html is a page, images, css, etc. are
assumed to be elments within that page.

    Very often, though, I've found that when one discovers that it will
be  difficult or impossible to proceed in the manner planned, the best
course of action is often to go back one step in the problem solving
process.  That is, to ask oneself "if I can't identify which hits come
from a single click, how else can I __________?", filling in the blank
with whatever you're really trying to accomplish.
--
Ray Morris
support@bettercgi.com

Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/

Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/

Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php