> For example, your replacement doesn't allow for parameters to be passed to > new() in the instance script. How long will that last? I predict that it I find passing params in new() essential. Most of the applications we develop here are "tools", where any given instance script sets a set of variables, and we'll have multiple instance scripts using the same modules. > > I wrote these modules because I am writing a rather large site > > infrastructure that will be running under non mod_perl blessed hosts. > > So speed and rigidity are my friends in this case. > > If speed is really your number one goal (and I'm not saying it should be), > consider dumping Template Toolkit and switching to HTML::Template. And if > you're ready for some real excitement, give HTML::Template::JIT a try. While I have nothing against H::T, he didn't say speed was his number one goal, just important enough to avoid unused features. While I haven't benchmarked anything, I suspect compiled TT templates are on par with compiled H::T templates. (so long as you aren't doing Bad Things in your templates). Since my environment also uses TT (our use of plugins and other features would render any H::T implementation a mass of nasty filters), I do approve of the idea of decoupling CGI::App and H::T. I'm also interesting in CGI::Light, since I'm not doing any html generation from CGI, but I seem to recall that it removed a bit too much... I'll check again. trimming out unrelated bit(H::T, html generation) I can use, but just pruning features means that I can do less. -- SwiftOne suppressed --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/suppressed/ 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.