At 05:34 PM 04/02/2002, Benjamin wrote:
You hardcoded the modename in every runmode, but if you put the
check into cgiapp_init, then you could do something like this (of
course you could use the same code in every runmode, or write a
subroutine, like Greg suggested, but if the code is placed
At 11:36 AM 04/03/2002, Jesse Erlbaum wrote:
Does this describe your situation? If so, why don't you simply
break your application into multiple applications, by required
authority? Each application could then have its own instance script.
At this point, you've lost much of the power of
Hey Greg --
At 11:36 AM 04/03/2002, Jesse Erlbaum wrote:
Does this describe your situation? If so, why don't you simply
break your application into multiple applications, by required
authority? Each application could then have its own instance script.
At this point, you've lost much
At 01:00 PM 04/03/2002, Jesse Erlbaum wrote:
Hey Greg --
At 11:36 AM 04/03/2002, Jesse Erlbaum wrote:
Does this describe your situation? If so, why don't you simply
break your application into multiple applications, by required
authority? Each application could then have its own
Hey Kenny --
The only question is flexibility. If I wanted to change the
delete_widget to allow a different group to have access to it
how would
I do that? Would I have to physically move the mode?
Here are the details. I have users in different groups with different
permissions.
On Wed, 3 Apr 2002, Jesse Erlbaum wrote:
I don't agree. Judiciously scoping application modules is one of the
cornerstone concepts in CGI::Application.
I originally tried to design Cascade (
http://summersault.com/software/cascade/ ) by grouping functionaly
according to the needed
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
I guess spell check though it would be better to call run-modes renamed :-)
Kenny Pyatt wrote:
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
At 02:21 PM 04/03/2002, Kenny Pyatt wrote:
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
