J. Erik Heinz wrote:
Hi,

Veikko Mäkinen <[EMAIL PROTECTED]> words
        on 18.11.2005 - 21:59 (+0200 Zulu-Time):


Session id is (usually) stored in your browser as a cookie and it's your browser who sends it to the server and agavi application within every request you make. Your browser doesn't know that it should store/send a

And heres my problem located. Normaly you attach the Session id in a
cookie or as get-parameter at the end of a link.
In agavi we have generated a session-id which is stored in the
table (database), but how do I get the already stored session-id out form the
table ?

The only addition Agavi does to PHP's normal session data management is the ability to save the session data to an SQL database. Other than that everything is done by PHP and not Agavi directly. PHP calls Agavi session handlers to read and write the session data. Normally it would just read/write from/to a file. The session id is sent as a cookie or get parameter just like it would be sent without Agavi. This is all done by PHP.

To get the session id (normally automatically generated by PHP) you'd use a built-in function session_id. BUT there's usually NO need to use it and surely there is never a need to query session data directly from the database.

If i have it the handling would be easy. I could have access to the
serialized BasicSecurityUser-object and manipulate it as i wish...

Serialized objects are unserialized automatically. If you stored an attribute to the user object, it will be there during the next request too.

Like I said before, it is clear that you are not familiar with session handling (PHP sessions in general, not just the way Agavi handles sessions) and should read a bit about it. Start by reading what the PHP manual has to say about it.


-veikko
_______________________________________________
agavi-dev mailing list
[email protected]
http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev

Reply via email to