Re: juggling multiple CGI::Application subclasses

[Cubes]

Our CGI::Application app has a couple of main sections, so I made a base class for each that contains all of the housekeeping I need for that area's subclasses: setup, teardown, cgiapp_init, cgiapp_pre/postrun, etc. Our auth stuff is in cgiapp_prerun.

In each subclass, I then "use base" the appropriate area's parent class, which gets me the auth & housekeeping stuff, override any functions (setup, for example) that need to be tweaked for the subclass, and add all the meat for the particular area of the app that subclass handles.

(Sorry I don't have time to go into a lot of detail, but hopefully this will get you pointed in a useful direction. I'll be out of town from tomorrow through the weekend, but I'd be happy to provide more info when I return.)

Edit: I should add that when I do the auth checks in cgiapp_prerun, I simply redirect to the login page if necessary, stashing away the intended URL in the database so the user can be redirected there after they sign in. This way I can keep the login handling routines themselves in their own tidy little module.