Actually you would store user specific data in either the Users's session or
the
User's OBJECTDATA field. Now that I think about it, however, now that
security is
changed this functionality may have changed. I am refering to
User.setTemp("id", object)
User.setPerm("id", object)
These methods should work thru Jetspeed 1.3a2. I still need to check out
1.4 to
what has changed.
r,
Hugh
----- Original Message -----
From: "Josh Hone" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, July 24, 2002 10:28 AM
Subject: Site policy issues
> Hi all -
>
> I have two general questions about policies for sites based on Jetspeed
and
> I would like to get the opinions, knowledge, and experiences of this
mailing
> list on them:
>
> 1.) Data storage format: You can mostly store personalizing data or
> portlet cuztomization data as strings in portlet parameters or as objects
in
> the Velocity context with Jetspeed out of the box. For example, I can
> remember my user's favorite sites as a collection of string parameters or
as
> a Sites object that wraps an array of sites. Which is the best general
> practice to use? Is it situational?
>
> 2.) What information do you find more practical to attach to a user as
> opposed to a portlet?
>
> TIA,
> Josh Hone
>
>
>
>
> _________________________________________________________________
> Send and receive Hotmail on your mobile device: http://mobile.msn.com
>
>
> --
> To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
