Has anyone else noticed that the cfflush tag is completely useless if you use the fusebox layout method? ...
I'm working on an application that was built by some other folks in fb2 ( though the same would apply if it were fb3 ) and they asked me to add an "ALL" button to a page which uses pagination... but because the potential exists that the contents of the page could be inordinately large ... ( thousands of results in the list query, with a gratuitous amount of cf code for each result ) , it may not be feasible to display the page without flushing the output buffer ... but cfflush can't be used inside of a <cfsavecontent> or <cf_bodycontent> tag, which is where the fusebox layout would necessitate it being, and even if it could, it would either display the content above the top of the layout (where it shouldn't be) or would display nothing at all until the page finished loading anyway, which was the problem necessitating the cfflush solution ... so my options are to leave it alone and risk things blowing up because impatient users continually hit the refresh button before the page finishes loading, or tediously extricate the content from the fusebox architecture and then have to maintain it separately... <sigh> ... this is very frustrating... Hey Hal, any thoughts on a revision to the fb3 suggested specification for layouts? Isaac Dealey New Epoch www.turnkey.to 954-776-0046 ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
