>
> I can iterate the username list in the application myself (as a matter
> of fact I have a reverse lookup table with user names and user sessions
> already for other reasons) but I don't know what to do when I've got the
> right session id. I could send the cookie manually but it seems
> stupid... Maybe I'm not clear enough, here's the (pseudo)code
>
> [$ if ($udat{username}) $]
> Hi, [+ $udat{username} +]
> [$ elsif ($fdat{username} || $fdat{password}) $]
> [- $session_id = find_session_id($fdat{username}, $fdat{password}) -]
> [$ if ($session_id) $]
> ...
You could try (untested):
[- tied(%udat) -> setid ($session_id) -]
> [$ else $]
> Invalid username or password
> [$ endif $]
> [$ endif $]
>
>
....
>
> I don't understand. Apache::DBI's persistent connection feature would
> lead to several Postgres childs per one Apache child which is clearly
> wrong. Are you referring to some other Apache::DBI feature? Looking
> right now at the docs but I don't see anything relevant...
>
Apache::DBI keeps a handle for any different connect string, so
dbi:Pg:dbname=x and dbi:Pg:dbname=y will keep two database handles open.
Just look at the source...
>
> Different virtual host have different session needs.
Yes, that's true. Originaly there was only one session object for
performance reasons. I agree that it is a good idea to have different
session setups and this will come one time, but at the moment I don't have
the time to implement it :-(
Gerald
-------------------------------------------------------------
Gerald Richter ecos electronic communication services gmbh
Internetconnect * Webserver/-design/-datenbanken * Consulting
Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz
E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131
WWW: http://www.ecos.de Fax: +49 6133 925152
-------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
