|
Patrick wrote: >This is important to me because I currently working on a >project where I'm receiving a XML document through sockets >programming. I append each sockets read (packet) to a >character hold variable. I'm told that once we start testing >production responses the XML document may be very large, >more than 65535A. If this technique gets passed that >limitation I code it that way now. If not, I'm open to >ideas. A few things to consider: If you're doing XML programming, then you should probably look at the "XML Interface for RPG" from Alphaworks. The URL is: <http://www.alphaworks.ibm.com/tech/xml4rpg>. Also, have you considered using the HTTP Server to process incoming documents? That way, you can avoid the sockets programming in RPG. (These may not help much with the 64K string limitation in RPG, but may help other aspects of the overall application design.) Cheers! Hans Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.