One of our recent CGI::Applications has been so useful for us that we've
created a second application with very similar functionality. The
second application piggybacks on the interface of the first, and several
runmodes (display_menu, etc) should be handled by the first application.
Easy enough, so far. My templates, however, have a number of places
where a script is not explicitly specified (href="?rm=my_run_mode"), and
I would like to keep them this way. I need a way to tell the second
application that it should call the first application when these
runmodes occur.
I think the best way to handle this is by creating a runmode in the
second application that can issue a redirect to the first application
when necessary. If I issue a redirect will the parameters sent with the
original request be sent on in the redirect? Do I need to do something
special to make sure they are?
Finally, is there a way to create a sort of AUTOLOAD runmode so that if
any runmode is called that doesn't exist in the specified application it
can redirect to a different application and try the requested runmode
there?
Ideas?
Thanks! =)
--TWH
---------------------------------------------------------------------
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.