|
On 12/28/05, albartell <albartell@xxxxxxxxx> wrote: > How big of an XML document (or how much over 16MB) could you realistically > see being sent to your iSeries and what does that document contain (i.e. > PO's, database sync info, etc)? The reason I ask is because there may be a > better approach to what is being done. better for whom? It is easier for the programmer to work with complex and large data structures when they are a single addressable object rather than a collection of segments. Look at how some of the list APIs are extra complex and not functional because all the objects in a library might not fit in the user space being listed to. > > XML can be quite the pig when it comes to size, but a 16MB+ document, well, > that's A LOT of xml :-) > more the reason to build the document as a string because appending to a string is much faster than writing to a stream file. -Steve
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.