Sean Davis wrote:
For those of you using path_info parsing to get at run_modes, how do YOU deal with the dynamic run_mode changes? It is easy enough to return $self->other_run_mode, but in the setting of using path_info, that seems contradictory and may even defeat the apache-based authorization concept (if done carelessly). I'm just curious as to what, in practice, people are doing.
Like I mentioned in another thread, I usually put all of my functions that are performed by the same group of users into the same module. That way I know that if I return into another run mode in the same module that the user will have access to it. I don't know if I'm missing the point of your question or not, but this has never been an issue for me.
As a side note, when would you ever have mode1 return mode2 and the user not have permissions to run mode2?
--
Michael Peters
Developer
Plus Three, LP
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.