I've put together the design for something similar and am waiting for project go-ahead at work to implement it. The design takes a different tack.
- There is a set of authorities which define every action a given user can take.
- Each user has a given set of authorities assigned to them.
- There is a given set of menu items which are all the items that can be put into a menu.
- Each menu item knows what authority(s) are necessary to have it displayed.
- A controller will have every menu item query the user object for its specific authority(s). The menu item determines if it should be displayed.
So, when you create a new menu item, you have it (and only it) know which authority combination is required for it to be displayable. If you don't want a menu item to be shown, you simply have the controller not put it in the list for querying.
Simple.
------
We are the carpenters and bricklayers of the Information Age.
Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose
I shouldn't have to say this, but any code, unless otherwise stated, is untested
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|