> Ooh...one important thing I forgot to point out about debugging. If your library functions are decoupled from "the web", then that means they're unit- > testable!
> Here at Novator, we have a standard I'm very obnoxious about enforcing: everything has a unit test. New functionality is added to a system in this > way: > a) write a UT in the module, to exercise the new functionality > b) run eval-ut, note the test is broken of course > c) change the module and run eval-ut on the command line constantly until > your tests are working > d) implement the xsp page, maybe make adjustments to UTs and functions to > support some calling semantics adjustments > e) throw together a basic xsl > Note the testing happens *before* you even get to XSP in (d). Heck, you don't even need to use a browser to write most of your "web application"! > With some newer code I'm just polishing up, we can actually start to unit-test web pages on the command line (including cookies, redirects, etc.). It was > a bit difficult, but it's very much worth it. These approaches will also work if you were using say CGI/mod_perl as your producer layer. > Sometime soon I hope to benchmark it, to verify this. Maybe in another month. I would be interested to see the benchmarks. It cant hurt to be faster ;-) JF ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com ********************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
