Mark,
Ok thanks. That clears some things up.
I was getting confused because in *my world* I have three .pm's: A Super.pm,
and an Admin.pm and User.pm based on Super. Each web page is a different
run_mode. The Admin run_modes mostly mirror the user run_modes but provide
administrative features as well. I guess I thought this was the intent of
CGI:App; to keep all the code in one place (module) for each site. But the
framework also makes it easy to have many instance scripts (with about 4
lines of code each) and still keep all the main parts under the hood in one
place.
> If I could figure out how to do it, I could put the cgi_prerun
> stuff into a
> superclass and inherit it across all the .pm modules.
I based my superclass from the examples in the pod. It was really pretty
easy. I think it's all there.
>
> If you want my session.pm you're welcome to have it. Like I said.
> I went off
> and did my own thing because I had my own idea about tracking sessions.
>
Sure, I'd love to take a look.
I'm also going to take a look at this CGI::Session::Auth mod. It sounds
promising even in it's infancy.
Again, thanks for all your input.
Bill
---------------------------------------------------------------------
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.