|
>I looked at it. Why do we have to try to cram every piece >of data into one transmission? Why not multiple calls? I think that would be worse than using XML, but that is just my opinion. Besides XML has so much more built into it like Schemas and XSL (XSL used for XML translations in this example). Are you going to tell your customer "Ok, first your going to send me Order=123, and when I respond with resp=success then you send me item=11111, and when I respond with resp=success you send me item=2222, etc. . ."? XML is so much more than just a buzzword and bulky. Does XML provide functionality that already exists, yes. But that functionality is incredibly enhanced over sending fixed length text files or name value pairs. I think that XML is overkill for really simple apps that could receive in a couple of form variables that aren't repeating and don't have to show parentage, but then you have to weigh if you want to deal with multiple methods of writing programs or just stick with one or the other. Aaron Bartell -----Original Message----- From: Brad Stone [mailto:brad@xxxxxxxxxxxx] Sent: Thursday, September 04, 2003 5:16 PM To: Web Enabling the AS400 / iSeries Subject: Re: XML vs. Name Value pair was ->RE: [WEB400] > I should have wrote the sentence as "...but to make my > point more valid let > me give you an example where I thought XML via POST would > be better than a > name value pairs via POST." I looked at it. Why do we have to try to cram every piece of data into one transmission? Why not multiple calls? That could be easily done with named pairs. Brad www.bvstools.com _______________________________________________ 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-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.