I agree. As far as the full image urls, I know for certain there are some bad urls in the HTML. Refer to my earlier post about how the HTML comes from a third party whom we have no control over. There are actually a mess of image 404s that go through every time we try to generate. At any rate, I believe those are related to today's problem... we have never had the cfdocument tag actually lock up like that before.
As far as the cfsavecontent idea-- this web service has the HTML passed in to it already generated, so there is no hold up on that front. ~Brad -----Original Message----- From: Jake Churchill [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 27, 2007 12:14 PM To: CF-Talk Subject: Re: cfdocument HELP! Some things that I've done to speed up cfdocument requests are as follows: * Check image links. Provide full URLs if possible. For some reason if an image is not found, it takes forever to render and display the little red x. * Minimize the display portion. I usually put everything into a cfsavecontent variable so all of my loops and things are generated into a single variable (sometimes multiples) and I display just one variable inside the cfdocument tag. This acts as a buffer and seems to speed things up on my servers. Jake Churchill CF Webtools 11204 Davenport, Ste. 200b Omaha, NE 68154 http://www.cfwebtools.com 402-408-3733 x103 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 and Flex 2 Build sales & marketing dashboard RIAâs for your business. Upgrade now http://www.adobe.com/products/coldfusion/flex2 Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:270832 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
