Re: Help prevent a ModPerl application from replacement by Java

If you're trying to win a race why are you using so many slow modules? Try again with CGI::Application, CGI::Application::Plugin::Apache, HTML::Template::JIT (or, sigh, HTML::Template::Compiled) and straight-up DBI. Be sure to pre-compile your templates and carefully examine your database calls with DBI::ProfileDumper.

And if that doesn't do it there's always Inline::C!

-sam

Comment on Re: Help prevent a ModPerl application from replacement by Java

Replies are listed 'Best First'.
Re^2: Help prevent a ModPerl application from replacement by Java by pg (Canon) on Aug 30, 2005 at 06:53 UTC
"And if that doesn't do it there's always Inline::C! Don't forget that Java has JNI. This is really not the point.	[reply]
Re^3: Help prevent a ModPerl application from replacement by Java by samtregar (Abbot) on Aug 30, 2005 at 16:51 UTC
I'd be happy to put Java's JNI head-to-head with Inline::C! Inline::C is superior in every way, in my experience. -sam	[reply]