Re: application security for users
From: steve (me_at_me.com)
Date: 05/01/04
- Next message: VisionSet: "Doing nothing with a methods argument - bad style?"
- Previous message: goose: "Re: crash during file writing, how to recover ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 1 May 2004 07:05:45 +0800
On Fri, 30 Apr 2004 19:59:51 +0800, FISH wrote
(in article <dbc5020.0404300359.741bf1c5@posting.google.com>):
> steve <me@me.com> wrote in message
> news:<0001HW.BCB792E70002E0D7F03055B0@news.newsguy.com>...
> [snipped...]
>> if i want to limit certain users to certain actions (add/delete/view),
>> what
>> is the best most transparent way to do this.
>>
>> is it to extend the button/menu class, to add a security check?
>>
>> For example, when the user selects the button/menu, the name of the
>> button/menu & the user name are passed to validate the security, if no go
>> the routine swallows the event, if go , it passes the event thru?
>
> You don't need to extend buttons or menus to do this. Just implement the
> checking functionality in the event handler for that Action.
>
> You might also like to disable the secured buttons and menu items, so
> they can never be activated to begin with. This will provide a visual
> clue to the user that the function is unavailable. You should not,
> however, use this as an alternative to the checks in the event handler.
> (Belt and braces!)
>
>
> -FISH- ><>
thanks fish
seems like a good place to start.
- Next message: VisionSet: "Doing nothing with a methods argument - bad style?"
- Previous message: goose: "Re: crash during file writing, how to recover ?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|