"Chappuis J.-Vincent" wrote:
> Furthermore, it's very usefull to use this getUser().setTemp, because I know
> now that I can rescue an object for example a vector of data, what avoids me
> reinterrogating the data base.
Good! That's what setTemp()/getTemp() methods were meant to be used. The objects
you put there will automaticly go away at the end of procesing the request.
If you need some object to live as long as a specific user is logged into your
system use HttpSession: data.getSession().setAttribute(String name, Object value)
(see Servlets JavaDocs from Tomcat for details)
If you want some object to be permanently associated with a specific user,
use data.getUser().setPerm()/getPerm(). This requires your user to have a valid
account in
the system because this object would be serialized and stored in Visitor.OBJECTDATA
field in the database when the session goes away.
These mechanisms can save you LOTS of database queries!
Rafal
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
