Hi folks,
>
> On Tue, 23 Nov 1999, David Guerizec wrote:
>
> > Are sessions and cookies part of the future releases of Midgard or do we
> > have to handle them ourself in a separate database ?
>
> PHPlib looks pretty good for doing session stuff in PHP (and thus
> in Midgard). I don't know where it stores it's information, though.
Yes, it seems to be pretty good at that.
And it stores information about sessions *and* users in a mysql database.
So it brings two problems :
1) Should I create two more tables (active_sessions & auth_user) in the
Midgard database or should I create a separate database for each vhost I
have ?
2) How to synchronize the user informations/authorization from
Midgard/Apache and PHPLib ???
These two questions made me think that it would be good to have a built-in
session manager into Midgard.
(And I really don't like URLs like
http://www.mydomain.com/path/to/page?session_id=afc45e6d9b23f5a...)
> Combined with the extendable records I guess you could say that
> Midgard 'supports' sessions. PHP has cookie support itself.
What do you mean exactly by 'extendable records' ? Users preferences ?
> Is there a specific need that isn't covered by this? Let us
> know.
No specific need for the moment, I just wanted to know how to do simple
session handling without using PHPLib, and instead using the apache's
capabilities (tell me if I'm wrong about apache's capabilities).
> Bye,
> Emile
>
Bye
[EMAIL PROTECTED]
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
