|
Multiple orders was just an example of having one repeating structure within another. For instance within our corporation we can have passed multiple prices and item numbers because we store it at the customer level, point company level, and prod company level. And being a printing company we also have a lot of text within each item telling us what to print on the product. Name value pair looses it's strength fairly quickly when you get into complicated scenarios (and there not even that complicated if you go back to your example of a relation database structure). It gets to a point where you say, "Do I want to use a widely accepted industry standard like XML or do I want to recreate this process for each method I receive orders?" XML has a lot going for it besides being a semi buzzword. There is _a lot_ of functionality being added to it constantly. I can't say how long it will be around, but it will definitely be around for the immediate foreseeable future. <Brad> Who wants to put forth the effort, make source available only to have it criticized because: "Its only RPG" or "You whould use DOW instead of DOU" or... </Brad> I wish I had that problem. I can't even get anybody to help with the code outside of my corporation. Open source within the RPG community is kinda an oxymoron. We should instead call it "Free tools within the RPG community". Aaron Bartell -----Original Message----- From: Brad Stone [mailto:brad@xxxxxxxxxxxx] Sent: Friday, September 05, 2003 8:19 AM To: Web Enabling the AS400 / iSeries Subject: Re: [WEB400] RE: XML vs. Name Value pair On Thu, 4 Sep 2003 22:45:10 -0600 "Nathan M. Andelin" <nandelin@xxxxxxxxxxxxxxxxxxx> wrote: > > What happens if the request contains multiple orders? > How do you say that > > LineItem1 belongs to the first or second order? Now > you are going to have > > to write some nifty parsing routines because parentage > is going to be a > pain > > in the butt. You will most likely have to build in a > multiple nested > array > > structure within your name value pair names or qualify > the heck out of > your > > names (&Order1_Item1=1234). No, you only get information on order at a time. Why try to drink from a firehose? What if you had 100000 orders. Are you going to spend 45 minutes building a 50meg XML file and send that across? No. Again, breaking it up logically makes sense here. _______________________________________________ This is the Web Enabling the AS400 / iSeries (WEB400) mailing list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/web400 or email: WEB400-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/web400.
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.