-----Original Message-----
From: gary menzel [mailto:[EMAIL PROTECTED]
Sent:
Thursday, 6 March 2003 1:53 PM
To: CFAussie Mailing List
Subject: [cfaussie] Re: CFMX Spider on Reboot

 


FOR INFO......

There were a set of articles in the Cold Fusion Developers Journal that had batch files to pre-compile all the CFM code to the cached Java classes (to avoid the big hit when doing large updates).  I cannot remember which issues thought.

 

Thanks. I'll check our archives.


Secondly.... just wondering what was meant by "
in the event of a server reboot" ?

The pages are compiled and cached in the webroot/WEB-INF/cfclasses directory.  A server reboot will not cause them to be compiled again.  The only way they will be made to recompile is if you change the file or delete the files from that directory.

In addition, the "tester" of the code would (should) generally be the first one to run the pages in the production environment (especially for a small number of pages).  So the performance hit will be experienced by people who are expecting it (overall).

 

Not necessarily. Code that is sent live to our production environment should already be thoroughly tested within the testing and staging environment. Added to this, we have 5 servers within the production environment. It's a big ask to perform an unnecessary hit across a large app on multiple servers.

 

Thanks,

Sarah.

 

---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]

MX Downunder AsiaPac DevCon - http://mxdu.com/
______________________________________________________________________
This email, including attachments, is intended only for the addressee
and may be confidential, privileged and subject to copyright.  If you
have received this email in error, please advise the sender and delete
it.  If you are not the intended recipient of this email, you must not
use, copy or disclose its content to anyone.  You must not copy or 
communicate to others content that is confidential or subject to 
copyright, unless you have the consent of the content owner.

Reply via email to