Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 28351 invoked from network); 8 Jul 2007 13:59:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Jul 2007 13:59:23 -0000 Received: (qmail 45585 invoked by uid 500); 8 Jul 2007 13:59:24 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 45521 invoked by uid 500); 8 Jul 2007 13:59:23 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 45510 invoked by uid 99); 8 Jul 2007 13:59:23 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Jul 2007 06:59:23 -0700 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=FROM_HAS_ULINE_NUMS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of spam_from_apache_dev_2@chezphil.org designates 77.240.5.4 as permitted sender) Received: from [77.240.5.4] (HELO japan.chezphil.org) (77.240.5.4) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Jul 2007 06:59:19 -0700 Received: from localhost ([127.0.0.1] helo=chezphil.org) by japan.chezphil.org with esmtp (Exim 4.67) (envelope-from ) id 1I7XHu-0003Jv-FF for dev@httpd.apache.org; Sun, 08 Jul 2007 14:58:58 +0100 Received: from localhost ([127.0.0.1]) by japan with smtp (dmsmtpd 0.00001); Sun, 08 Jul 2007 14:58:58 +0100 From: "Phil Endecott" To: Date: Sun, 08 Jul 2007 14:58:57 +0100 Subject: PostgreSQL authentication in 2.2; caching? Message-ID: <1183903137952@dmwebmail.japan.chezphil.org> X-Mailer: Decimail Webmail 3alpha16 MIME-Version: 1.0 Content-Type: text/plain; format="flowed" X-Virus-Checked: Checked by ClamAV on apache.org Dear Experts, A few days ago I posted a question with this subject on the users lists, but have got no replies: http://thread.gmane.org/gmane.comp.apache.user/69944 The summary is: - Currently I'm using 2.0 with a 3rd-party mod_auth_pgsql. - In 2.2 I would presumably use the core DB-backed auth framework. - As far as I am aware, the core DB-backed auth modules don't implement caching of credentials. The 2.0 mod_auth_pgsql that I'm currently using does have this, and it's essential for my application. - There is a mod_authn_cache at http://mod-auth.sourceforge.net/docs/mod_authn_cache/ but it looks a bit abandoned; does anyone know anything about it? - Ideally I would also want the cache to be flushed when the database is changed; this could be done using PostgreSQL's asynchronous notification feature. I imagine that I would have to do this myself. I mentioned this here ages ago when I first considered moving to 2.2: http://thread.gmane.org/gmane.comp.apache.devel/23903/focus=23904 If anyone would be interested in helping me implement this I would love to hear from them. Any thoughts anyone? Regards, Phil.