Re: XMLSAX procedure parameter length -- RPG400-L

× 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.

Subject: Re: XMLSAX procedure parameter length
From: Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
Date: Fri, 19 Nov 2004 15:55:05 -0600 (CST)
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

> The XML file I am working with has an embedded PDF file that is over
> 100K bytes long.

It has a PDF file embedded inside XML tags?  What happens if there's a <
or > character in the PDF data?  What if there's a non-text character in
the PDF data?  Or is the whole thing encoded so that it's legal?

It would be possible to use eXpat for this -- though my wrapper procedures
are similarly limited to 32k, if you use eXpat directly, there'd be no
limit.

It's a thought, anyway..

As an Amazon Associate we earn from qualifying purchases.

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.