Andy Clark wrote:
An amendment to my previous post:
While the only safe way to make sure that DOM strings are
intern'd is to provide your own DOM implementation that does
that work, it is important to note that Xerces *does* intern
strings for element and attribute names (among others) and
the DOM implementation creates nodes with those strings. So
the important strings will be intern'd but for a portable
app, you can't rely on that. On the other hand... in order
to change the DOM implementation used, you have to rely on
a Xerces-only property. This is what Star Trek fans call a
"dilemma". ;)
Thank you Andy,
It seems then that my request is resolved as this is already occuring on
the dom element names and attribute names. I should focus on using
something else then so as to reduce my memory problems using a caching
system rather than making a new dom implementation which already
performs what is said above. I can see that I can serialize dom so this
as initial idea is good. I could possibly write my own dom
implementation that uses serialization to cache vast amount of data that
are not used frequently...
Regards,
Georgios C. Kossionis.
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
| 
