|
I have to admit than when I read the start of this thread, I said to myself "huh? trying to force an XML document into a data queue? that'd be awkward..." It would certainly make more sense to use a vehicle that is capable of working with the data as a "stream" rather than as a "record", and this would mean using sockets for communications and stream files for storage. In fact, if you're receiving the data from a web server via sockets, writing it to a stream file is REALLY simple. (In fact, the sockets tutorial that I'm writing uses that as one of the first "getting started" examples) On Tue, 24 Jul 2001, Bartell, Aaron L. (TC) wrote: > > I guess my other option would be to make it as big as possible. Is there > any performance considerations with this? I would be wasting a lot of space > for each data queue entry. > > Maybe I am going about this all the wrong way. Instead of trying to fit my > whole XML string into this data queue maybe I should just write the XML > string out to a stream file in the IFS and put the path to the file in the > data queue and have the program monitoring the data queue go and get it from > the IFS. > > Thinking hard, > Aaron Bartell > +--- | 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.