FILE I/O happens with every page request. Every page has to be loaded from the disk, every cfinclude loads a file off a disk, every use of a custom tag, has to loa dthe tag file. Rather hard to avoid I/O
Russ -----Original Message----- From: Brad Wood [mailto:[EMAIL PROTECTED] Sent: 21 February 2006 17:39 To: CF-Talk Subject: RE: cfsavecontent and cfqueryparam I thought about that, but didn't mention it. File I/O can be hideous for performance if you are doing this a lot in an environment which needs to be fast. I would consider it a last resort. This could open up even more doors for code insertion. ~Brad -----Original Message----- From: Jim [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 21, 2006 11:33 AM To: CF-Talk Subject: RE: cfsavecontent and cfqueryparam just thought of a nasty workaround (untested): write it to file then include it! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:233076 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
