P
Peter Rilling
There are some issues with what you want to do.
1) Xml is loaded entirely into memory when the DOM is created and then the
connection (generally) is lost from the physical file.
2) Two applications live in different processes and therefore cannot share
a references to the same object. On application cannot subscribe to events
for an object created in a different application.
I am not familiar with remoting, but you might need to use that to
facilitate the communication. Or you might try implementing a COM+ object
that runs as an application, then more then one application might be able to
get a reference to that object which would then wrap operations on the XML
file.
"Chau Johnthan"
1) Xml is loaded entirely into memory when the DOM is created and then the
connection (generally) is lost from the physical file.
2) Two applications live in different processes and therefore cannot share
a references to the same object. On application cannot subscribe to events
for an object created in a different application.
I am not familiar with remoting, but you might need to use that to
facilitate the communication. Or you might try implementing a COM+ object
that runs as an application, then more then one application might be able to
get a reference to that object which would then wrap operations on the XML
file.
"Chau Johnthan"