Re: User permissions in app
Re: User permissions in app
- Subject: Re: User permissions in app
- From: Nathan Dumar <email@hidden>
- Date: Thu, 11 Nov 2004 15:04:04 -0500
I put the user object in the session, and follow relationships to any
other objects as needed. It fits my needs better. If the statusLevel
is the only thing you'll need throughout your whole session, then
there's no need to use anything else. It all depends on what you need
to make your design work.
Take care,
Nathan
On Nov 11, 2004, at 10:16 AM, Jeremy Matthews wrote:
I want to determine visibility of available options through
WOConditionals, based upon login. Right now I have a primary table
with all sorts of great data, and a separate table for other
attributes, including "statusLevel". From what I gather, I pull the
user (records') corresponding attribute "statusLevel" from the DB, and
assign that within the session. Is this correct, or is there a better
way?
Also, please don't supply any code quite yet. I'm starting to get the
hang of some things. I'll save that as a last resort. Just ideas for
the moment would be greatly appreciated.
Thanks,
-jeremy
_______________________________________________
WebObjects-dev mailing list
email@hidden
http://www.omnigroup.com/mailman/listinfo/webobjects-dev
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden