> Memory deallocation, from my experience, happens at the > end of a request. It makes sense that way, and that would > be how I would implement the CFML interpreter engine anyway > since all the engine needs to do is to keep track of the > heap memory assigned to the thread performing the CFM > request, and just return the heaps back to the heap pool > when the request ends. I think Allaire/MACR used to call > them SmartHeaps. Pretty funny name. ;)
I suspect the name came from the product they were using to manage memory: http://www.microquill.com/ Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ::::::::::::: dream :: design :: develop ::::::::::::: MXDC 02 :: Join us at this all day conference for designers & developers to learn tips, tricks, best practices and more for the entire Macromedia MX suite. September 28, 2002 :: http://www.mxdc02.com/ (Register today, seats are limited!) :::::::::::::::::::::::::::::::::::::::::::::::::::::: ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. 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
