Re: auth_rewrite authenticate.c user_auth_hash_pointer usage

Right. The proxy_auth dlink is obsolete -
I thought I'd #ifdef GLOBALPROXYHEADERCACHE but obviosuly I haven't.
The point was to allow multiple references back to a single structure that need to be cleaned all at the same time.

Aliases: a single scheme's auth_user->scheme structure can potentially have aliases - multiple auth_user structures pointing at it
(and return different usernames). It's not supported by any of the current modules, and may need a little more API tweaking to work
fully. As far as memory usage goes - I was going off the fact that 10,000 users, will only use ~2M of memory.

I'm quite happy to memory-tune the code vs flexability though.

Rob

----- Original Message -----
From: "Henrik Nordstrom" <hno@hem.passagen.se>
To: "Robert Collins" <robert.collins@itdomain.com.au>
Cc: <squid-dev@squid-cache.org>
Sent: Sunday, January 14, 2001 9:54 AM
Subject: Re: auth_rewrite authenticate.c user_auth_hash_pointer usage

> Robert Collins wrote:
> >
> > Two reasons:
> > Aliases
> > Header caching.
> >
> > The second reason is now obsolete, but the first isn't.
>
> Can you please elaborate? The dlink list there is completely unused in
> the current code, and the hash is built on the username from the
> auth_user structure the indirect pointer points at.
>
> /Henrik
>
>
Received on Sat Jan 13 2001 - 16:44:38 MST