I read through HTML::FillInForm and have to admit that it would be a nifty solution. I can see pros and cons, however.

Pros: As the HTML would be left relatively pristine, it would be much easier for our designers to work with it. Further, as the HTML changes, there would less synchronization. This is a huge win. This also appears to be a relatively easy solution to implement.

Cons: We're running in an ISAPI environment here. While that's faster than straight CGI, it does not compare to the performance of mod_perl. Until such time that we can convince the Powers That Be that mod_perl (and Apache, and Linux and ...) is the way to go, we have to be careful about the performance of our applications. Already, using Template Toolkit is a serious issue, in terms of performance. I'm concerned that HTML::FillInForm would be the death knell. Any experience with how this might affect real-world performance? It seems to me that inserting the template markup tags directly into the HTML document would be the least performance-intensive alternative.

Cheers,
Ovid

Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.