I transmit through a socket. And now that you mention it, ya, I could go that route. Sometimes you don't see those options unless they hit you in the head :-)
It seem strange though (inconsistent) that I can serialize it through a socket when I can't parse it from a socket. If I recall from the XML spec correctly, I believe
only one root node is allowed in a document. If thats correct, couldn't Xerces use that to (at least in v2) complete the parsing and return control to the
calling application?
Thanks,
-P
| Andy Clark <[EMAIL PROTECTED]>
10/23/2001 10:32 PM
|
To: [EMAIL PROTECTED] cc: Subject: Re: Xerces serialization memory usage (and related stuff) |
[EMAIL PROTECTED] wrote:
> I need to transmit an XML string from data that I have put into
> the DOM.
What do you mean "transmit"? If you want to create a file
from the document or stream the serialized form of the
document, then why waste all of the memory and time by
writing it to a String just to save it out again. You
should write directly to where the data needs to go.
> Are you saying that Xerces is not a good choice to implement this and
> should I be doing this by hand then?
It doesn't have anything to do with Xerces -- it's the
nature of the serialization process and the fact that you
are writing it to a String.
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
