On Tue, 22 Mar 2005 14:06:08 +1100, Andrew Scott <[EMAIL PROTECTED]> wrote: > guess would be that after looking at several cf cached templates the problem > is going to be that the translation to java byte code is till needing some > tweaking for speed and optimization.
Aside from the fact that decompiling the Java bytecode is almost certainly a violation of the license(!), yes, if you compile down from a high-level language to a low-level language, you'll never be as efficient as having written something in the low-level language in the first place. There's always room for improvement and that's the price you pay for the speed of development in ColdFusion over Java (or assembler). > For example cffile, every time this is used it opens and closes the file > every time this tag runs and you add that up over a few megabytes and the > execution time will sky rocket. If you're appending lines to a file then this might be an issue but aren't we talking about reading and parsing the log file here? If so, a single <cffile> will read the entire log file into memory - so the execution time issue is not applicable here. The parsing of log files is a different matter. CF relies on Java string operations and those are not really intended for massive parsing / manipulation operations unfortunately. Perl (not "pearl") is built on top of highly optimized string manipulation libraries and is specifically designed for parsing text. As for the question in the subject line - ColdFusion is very robust but, like all languages, there are some tasks for which it is better suited than others. -- Sean A Corfield -- http://www.corfield.org/ Team Fusebox -- http://www.fusebox.org/ Got Gmail? -- I have 48, yes 48, invites to give away! "If you're not annoying somebody, you're not really alive." -- Margaret Atwood --- You are currently subscribed to cfaussie as: [email protected] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
