|
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.
case 2: Some of the screens keep nodes information so the user can update them. The document itself is not kept
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.
Reuven Nisser Gareth Reakes wrote: Can you explain a bit more about why you need to release the document? You should not release it until you don't need to access any of the contents. |
- Migration fro MSXML4 Reuven Nisser
- Re: Migration fro MSXML4 Axel Weiß
- Re: Migration fro MSXML4 Gareth Reakes
- Re: Migration fro MSXML4 Reuven Nisser
- Re: Migration fro MSXML4 Gareth Reakes
- Re: Migration fro MSXML4 Reuven Nisser
- Re: Migration fro MSXML4 Alberto Massari
- Re: Migration fro MSXML4 Reuven Nisser
- Migration fro MSXML4 Reuven Nisser
