Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Date: Sun, 20 Jun 2010 23:31:20 +0100
From: Nick Kew <nick@webthing.com>
To: dev@httpd.apache.org
Subject: ap_socache anomaly (Re: mod_authn_cache)
Message-ID: <20100620233120.741e9838@baldur>
In-Reply-To: <036A2CB2-F2FF-494E-971D-B15AF3734880@sharp.fm>
References: <20100616232934.300087a4@baldur>
	<036A2CB2-F2FF-494E-971D-B15AF3734880@sharp.fm>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Thu, 17 Jun 2010 00:43:55 +0200
Graham Leggett <minfrin@sharp.fm> wrote:

> mod_socache all the way.

Question on mod_socache usage: how to use create/init/destroy?

Create seems straightforward, but init/destroy are contradictory.
On the one hand, they are passed a server_rec, suggesting they're per-server.
On the other hand, the instance comes from "create", and the cname argument
suggests it should be per-module.

Grepping /trunk/ finds only the providers, no usage examples!
Looking at one of the providers, the server_rec seems only to be used
in ap_log_error.

Is it safe to assume the server_rec won't be used for anything more?
And why not take the apparent mismatch out of the API by using
ap_log_perror instead?

-- 
Nick Kew