in reply to Re^4: User access controlled by subroutine attribute.
in thread User access controlled by subroutine attribute.
I see it as protection from developer error. You probably want to have authorization handled in a way that allows you to both restrict the overt choices that a user can make and also to give the user a more friendly message up front, which all probably requires explicit coding nearer the front end. However if there is the possibility of an unintended method getting called (a typo in a dispatch table or an unchecked action parameter for instance,) then you might feel it is appropriate to prevent that method being called by unauthorized users. Call it a belt and braces approach.
/J\
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^6: User access controlled by subroutine attribute.
by rlb3 (Deacon) on Aug 15, 2006 at 14:50 UTC |