× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



On Tue, Mar 31, 2020 at 10:55 AM Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

Barbara will know for sure but I know at one time when I had a file with an XML error that XML-SAX rejected it, which would imply at least some form of complete file processing prior to returning actual data.

This is tickling something in my memory. Somewhere in these lists, I
can't remember and can't find where (did some searching just now),
there was at least one discussion about the relative strengths and
weaknesses of the DOM approach vs. SAX approach to XML processing. And
while there was broad agreement that DOM strongly implies "document as
a whole" (and thus, in principle, greater memory requirements than
SAX), I think we concluded that it was a mistake to conflate the
"XML-INTO vs. XML-SAX" picture with the "DOM vs. SAX" picture.

It would not surprise me if you or someone else revealed that both of
the RPG opcodes had some common machinery underlying their
implementations, particularly since they both accept handlers.

John Y.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.