This is one of those

JeevesBond — Tue, 28 Oct 2008 14:16:38 +0000

This is one of those subjects where I'd like to hear Abhi's opinion too.

Serialising methods isn't harmful, but storing a whole user class instance is a little inefficient. Most user state information should already be recorded in the database, pretty-much all you need in $_SESSION is the user id, a datestamp of when they performed their last action (if you want a who's online widget), and other stuff relating to just this session, a message to display to the user, for example.

I tried this out myself, and PHP sensibly just stored the object's state, i.e. it guessed what I wanted and did it. So, what you're doing is convenient, but it is possibly storing a little more information than you need.

I'm not sure why you would

pr0gr4mm3r — Mon, 27 Oct 2008 01:30:55 +0000

I'm not sure why you would want to store an object with methods. I sometimes store profile information (user id, email, whatever) in the session, but it would be an assoc array or data object.

All other things I store are just variables.

Methods (most of them could

teammatt3 — Mon, 27 Oct 2008 01:09:09 +0000

Methods (most of them could be removed since they are just accessors) and values. Why do you ask?

And if you're not putting objects in sessions, how do you manage state data (besides putting each piece of data into a separate session var)? Are you manually serializing it? Are you keeping everything in a database with the sessionID as the primary key?

In other languages, the

pr0gr4mm3r — Mon, 27 Oct 2008 00:42:03 +0000

In other languages, the objects had to be serializable, I think. In PHP, I think as long as the object isn't anything to do with something instance-based, like a MySQL connection, you're fine.

Does your object just have values, or are there any methods?