Re: XML-SAX *XML_EXCEPTION event and reported parsed length question

I suspect it has t work that way and since it also uses Java, I suspect it is a lot slower than the C code used behind XML-SAX.

I know that some of the database guys would like to see the Java code in this (and areas such as web services and JSON) replaced by C/C++ because they are seeing performance issues.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On Jul 13, 2017, at 3:40 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

Don't forget there could be hundreds of thousands of those "callbacks",
depending on the size and complexity of the XML document, assuming I
understand that is how XML-SAX works. The overhead of that large a number
of callbacks will likely vastly exceed the overhead of calling XMLTABLE a
few times if you had, for example, three sets to extract.

Mike, don't you think that XMLTABLE uses the same type of callback
processing under the covers? If not, then do you have a guess as to what it
might be doing under the covers?
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD