I thought about that. Besides the fact that it will require me to pre-parse the HTML, store the images locally, and then modify the HTML to point to the new location, which seems to fundamentally defeat the point of having cfdocument do it for me-- I haven't proven that CFHTTP won't suffer from the same problems since it probably uses the same Java libraries in the back end.
~Brad -----Original Message----- From: James Holmes [mailto:[EMAIL PROTECTED] Sent: Thursday, May 17, 2007 10:22 AM To: CF-Talk Subject: Re: cfdocument hangs on slow images Perhaps getting the content and the images via CFHTTP, outside of the CFDOCUMENT tag, will yield better results. This way the images will be local and the cfdocument tag won't be locked up. On 5/17/07, Brad Wood <[EMAIL PROTECTED]> wrote: > I'm waiting for your "good ideas" James.... :) > > ~Brad > > >All right, you asked for it. > > > >I was actually hoping to contain any conversation which arose to one > >specific place since in the past it has been difficult to carry on two > >conversations about the same topic on two separate forums. > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJQ Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:278458 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
