> However, when the "by whom" can change often, and the "access groups"
> have to be broken up and rearranged, you can either be helped by your
> access control logic, or hindered by it. I'd much rather change the
> access control in the mode than have to move the run mode to a
> different application and then have to change everything that refers
> to it. Moving run modes from app to app also makes it much more
> difficult to follow the revision control history of the application.
I am encouraged, by the spirited discussion, that my question was not a
stupid one.
I am controlling authorization/sessions mostly via a SQL database
with logic built into the app to check the users permission via a
relationship query. I needed a way for each renamed to tell me who it
was for that part of the query.
I am grouping each module by function. I am also doing all of the
authorization/session handling via a separate module. To change
permission I update the SQL Database to reflect a new relationship
between the user and a role and the role and a renamed.
I think there are several valid solutions to this problem. I have
used Apache::Session with CGI::App on some of the other apps I have
developed. I will probably incorporate Benjamin's suggestion on the
dynamic permissions check in cgiapp_init to stop incorrect entry in each
mode.
I am only a purist in two things:
1.) Is has to work according to the spec.
and
2) They have to pay me for it.
Thanks,
Kenny Pyatt
President
Design Shack
www.dshack.com
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[email protected]/
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
