> If You use cookie or browser pop-up auth, then user > is autenticated > per page, until the browser is closed AFAIR.
But on http://www.midgard-project.org/manual/en/function.auth-midgard.php I read: "The Midgard code will not see the difference between a user logged in by HTTP authentication or the cookie login (although you can examine the MidgardLogin cookie to see if it's been set). If the optional sendcookie parameter has been set to zero (FALSE), Midgard will only authenticate the user for that particular page, and will not send an authentication cookie to the browser." So I assumed that if I set if the cookie is set with true (or "1") as third parameter, pages requiring authentication wouldn't send an authentication request anymore, but rely on the cookie. > You need to have some special user info which is > directly > "connected" to user and its cookie. At last I did > that, and it works fine. > Manipulating with cookies and user records could be > very usefull here. > I used $person->topic for that which is named from > timestamp cookie > when the user came first time. You have cookie so > get_topic(article)_by_name(cookie) > and then check who is owner etc etc. No record with > cookie means - > user is not authenticated. Wow! So every time a user logs in, you create a dummy article with the user as owner and use the name field to store the cookie... (while cleaning up previous user sessions I assume...). And for every request you read the cookie and figure out which user is sending the request... I had hoped there would be an easier built-in solution... ? Regards, pascal __________________________________________________ Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more http://games.yahoo.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
