Note that if the heaps are never, ever released, it might be because the application still has a reference to an MSXML object - in that case, you'll see that the module is never unloaded, and of course its resources are never released.
e the document.write's with a MsgBox because its not running in the browser but I get an error that an object is required. I was hoping to learn about doing this starting with these simple ex
There was another issue as well. The MXXMLWriter stores all of its output in a string property called output. This is where we encountered the next major Big O issue in developing our server application. Every subdocument is stored in memory as MXXMLWrite
I decided enough is enough and created an actual class that handles more things. clsXML.asp is the actual class and objXML.asp is an implementation of the class. It can actually be used in a huge variety of ways. For example, if there is a need to store