Jon Paris

On Feb 23, 2019, at 2:59 PM, John Yeung <gallium.arsenide@xxxxxxxxx> wrote:

On Sat, Feb 23, 2019 at 10:36 AM Jon Paris <> wrote:

Given the earlier description of the file in question John I don't see memory as an issue

Because it's small enough?


besides if it were using XML-INTO with a handler would give "row by row" access and a tiny memory footprint.

I'm not familiar with XML-INTO, and I certainly don't know about
handlers. Row-by-row access doesn't make sense to my understanding of
what DOM is. I'm not doubting you at all; I imagine you've done this
yourself already many times.

Now you've confused me. You were talking about SAX being better for selectivity and I asked if you meant DOM. SAX doesn't let you be selective other than in the sense that you can simply ignore every element you don't want. Other than the starting point for the parse there's nothing selective you can do with XML-SAX that you can't do with XML-INO - that's all I was saying.


Maybe XML-INTO isn't strictly DOM?

XML-INTO isn't DOM at all. It is basically built on top of XML-SAX. It simply allows you to be selective about which elements you want to process rather than have to code logic to decide which to ignore/process.

I believe the XML Toolkit offers DOM capabilities but I've not used them except when it first came out.

John Y.
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support by shopping at with our affiliate link:

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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

This mailing list archive is Copyright 1997-2022 by 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.