Greetings, First off, I want to thank John Drago for his assistance with managing Apache::ASP sessions external to the environment.
My question this time is more religious/philosophical than it is technical. I have inherited a legacy web application that runs on Apache::ASP. The application was designed in 1998-2000 by developers that weren't very familiar with perl. As a result, there are a lot of design flaws that need to be worked around. The most notable design flaw is the tight integration between the application and the display. Perl code is directly intermingled with the HTML page, making the external management of the page elements nearly impossible. While I know that this is what Apache::ASP is about and sometimes doing the above is desirable, I also know that it makes ongoing page maintenance for nontrivial sites a nightmare. One possible workaround is using a simple perl templating library (such as HTML::Template). However, this "feels" to me to be somewhat redundant when using Apache::ASP in the first place. I guess the root of my question is this: how do *you* prefer to abstract the application and display components in your Apache::ASP applications? Are there standard, "accepted" ways of doing this? Thank you very much in advance for any tips and advice. Steve __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
