8 messages in net.sourceforge.lists.courier-usersRe: [courier-users] feature request f...
FromSent OnAttachments
Olivier PoitreyDec 7, 2001 6:35 am 
Stephane EntenDec 20, 2001 2:19 pm 
Aly S.P DharshiDec 20, 2001 2:26 pm 
Sam VarshavchikDec 20, 2001 2:39 pm 
Stephane EntenDec 20, 2001 3:28 pm 
Olivier PoitreyDec 20, 2001 4:23 pm 
Todd LyonsDec 20, 2001 6:24 pm 
Mike HorwathDec 21, 2001 7:29 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] feature request for authdaemon: cache mechanismActions...
From:Stephane Enten (tu@mmania.com)
Date:Dec 20, 2001 2:19:39 pm
List:net.sourceforge.lists.courier-users

On Fri, Dec 07, 2001 at 03:35:37PM +0100, Olivier Poitrey wrote:

Hello,

Authdaemon system don't seem to have any cache system. For authmethod that need database access, I think that it's not really powerfull. What about implementing a cache mechanism in authdaemon ?

I'm sorry if it is already in the TODO list.

What about this unanswered request ?

I think many of us using some database (ie. MySQL or LDAP) would really like to have authdaemond make use of the fact that he's persistant.

When it comes to tens or hundreds of queries per second, having some caching would save us some serious load on the database server(s).

Another great benefit of a caching engine would be that DoS'ing the database by hammering the services with authentification requests would become a lot more difficult.

Regards,

Stephane