Hi,
Reuven Nisser wrote:
Hi Gareth,
case 1: I have a caching mechanism which "gives" nodes to different
routines. The user might force cache re-read but some of the nodes might
be still in use.
If I understand you correctly then you are saying that memory management
of the old documents are taken care of by some kind of reference
counting? Xerces does not do this - you will have to maintain a list of
documents and release them when they are finished with.
case 2: Some of the screens keep nodes information so the user can
update them. The document itself is not kept
You can get the owner document from any node so thats not a huge problem.
These are examples and you might think it's wrong strategy but it works
with MSXML. To migrate to XERCES I prefer not to re-write the whole code
(which is time consuming and will insert bugs) but change just the basic
XML classes I am using.
If you have a long running application and you are going to keep
reloading documents then you are going to have to release them at some
point. You are going to have to replace the garbage collecting
functionality of MSXML. Take a look in the mail archives though as I
recall some people talking about implementing reference counting on top
of xerces a while ago.
Gareth
--
Gareth Reakes, Managing Director Embrace Mobile
+44-1865-811197 http://www.embracemobile.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
