I agree, this looks like it would be best suited to a standalone script.
If you really want this to be a mod_perl module, why don't you do something like check the timestamp of the JS/CSS file and cache (Cache::FileCache) the minified version of the file until the timestamp on the original file changes at which time you would reprocess the file. This way, you only have to process the file once and performance becomes a non issue - although being able to process the file once with XS may be advantageous to some if they have a very large JS/CSS files. Andrew ----- Original Message ----- From: "Ask Bjørn Hansen" <[EMAIL PROTECTED]> To: "Graham TerMarsch" <[EMAIL PROTECTED]> Cc: "modperl List" <modperl@perl.apache.org> Sent: Sunday, October 21, 2007 7:42:38 AM (GMT-0500) America/New_York Subject: Re: ANNOUNCE: XS-based minifiers for JS/CSS On Oct 16, 2007, at 1:24 AM, Graham TerMarsch wrote: > After receiving some feedback from people about my Apache2 auto- > minification > filters for JS/CSS, and seeing that the only issue people seemed to > have was > that the underlying minifiers weren't terribly fast, I've gone > ahead and have > rebuilt them using XS. Why do this dynamically at all? (versus just doing it once on deployment / restart / whatever). -- http://develooper.com/ - http://askask.com/ -- Andrew Wyllie Dilex Networks, LLC [EMAIL PROTECTED] 866-479-4591
