You can easily read the XML using TCP/IP yourself and find the ending tag,
process, read the next document, process, etc. We do that always (much easier
than other ideas). You know the ending tag from the starting tag and there are
issues about blocking and non-blocking reads. We read one byt
Like I said, read into a string, then parse that. You can skip the garbage
like CR/LF … in our case if it all goes into the string in one read then so
what, we still parse them one at a time … Eric
From: xml [mailto:xml-boun...@gnome.org] On Behalf Of Webb Scales
Sent: Monday, September 09,
Thanks, Eric -- that's an interesting suggestion.
Does this work for you because the '<' character is not permitted in the
stream except as the opening of a tag (which makes it very
straightforward to locate each tag) and the root tag is not permitted to
appear inside the document (or, are you
On Tue, 2019-09-24 at 17:29 -0400, Webb Scales wrote:
> Thanks, Eric -- that's an interesting suggestion.
>
> Does this work for you because the '<' character is not permitted in
> the stream except as the opening of a tag
This isn’t true in general in XML, so beware.
19
On 9/24/19 5:49 PM, Liam R E Quin wrote:
This isn’t true in general in XML, so beware.
That was why I was asking :-)
(And, it's why I really want LibXML2 to do as much of the thinking here
as possible!)
Thanks,
Webb
--
Webb Scales
Principal Software Architect
6
