I've just started digging into CGI::Application and thinking about how to architect a small project of my own. Sorry if this is too basic, but Google didn't help me and this thread may help others.
One question came to mind: I generally prefer to use one or two main .shtml files to give a site a basic layout, include all the style features. I then use Server Side Includes (SSI) to call on CGI scripts to build up portions of the page's content. I don't like making CGI scripts that output entire HTML pages. Also, though I know it's mostly irrational, I also don't like the ".cgi" appearing in a URL that people may end up cut-and-pasting to make links. At most, "http://foo/?bar=4"; should clue the application if a parameter must be included in the URL. How compatible are these approaches? Can I make my CGI::App "run modes" implement only certain panes of an overall SHTML layout? If the pane wanted to provide a link to forward users to some other run mode, can I easily control the URL construction? [ e d h a l l e y ]---------------------------------------------------- --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
