Re: [cgiapp] submodes?

["A.M." <suppressed>]

---->>>
On Thursday, October 31, 2002, at 05:14  PM, Spencer Christensen wrote:

> Quoting "A.M." <suppressed>:
>
> > I like CGI::Application- I really do, but for me it really is missing
> > an extra layers of modes for clarity and security. Let me give an
> > example. Consider a multiuser system with users:
> > admin
> > schmo1
> > schmo2
> > I could implement this using CGI::Application as follows (in sub 
> > setup):
> >    $self->run_modes(
> >                     login=>'login',
> >                     adminpage1=>'adminpage1',
> >                     adminpage2=>'adminpage2',
> >                    schmo1page1=>'schmo1page1',
> > 		....
> >                     );
> > However, the runmodes are still "visible" to other users. I have using
> > Apache::Session and authenticating the user every time (which needs to
> > be done anyway) but the the above solution doesn't look "clean". I
> > would like to be able to write:
> > $self->mode_params('user','item');
> >    $self->run_modes(
> > 		login=>'login'
> >           		admin=>{
> > 			page1=>'page1',
> > 			page2=>'page2',
> > 			},
> > 		schmo1=>{
> > 			page1=>'page1',
> > 		....
> >                     );
> > The extra layer saves me typing
> > I suppose I could reroute using cgiapp_prerun and check for the second
> > CGI param (here "item") or I could just have one runmode per user and
> > grab the second one myself, but isn't that clunky and sort of what
> > using CGI::Application is supposed to mean? If I use the second
> > solution then I have as many runmodes as user types but potentially
> > thousands of runmodes. Thoughts or suggestions for improvement on my
> > part?
>
> Hello AgentM,
>    Why do you need a run mode for each user and each page combination? 
>  Are the
> run modes that different from each other?  Or are you repeating code 
> in a lot of
> places?
Right. The "users" may not necessarily map to specific users- perhaps 
"user type" or  "group" is the better term. I usually have an admin, 
some upper-level users who manage lower-level users, and the 
lower-level users. I am also hesitant to put the runmodes in the same 
hash since a slip of my authenticator (based on sessions) could allow 
unprivileged users unauthorized access. A second hash level would 
alleviate this though I would still use my authenticator.
> -spencer christensen
> suppressed
>
> ---------------------------------------------------------------------
> Web Archive:  http://www.mail-archive.com/suppressed/
> To unsubscribe, e-mail: suppressed
> For additional commands, e-mail: suppressed
><><><><><><><><><
AgentM
suppressed




---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed