×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I do a fair amount of building web pages using XSLT, so in a lot of my stuff I pass JSON back to the browser from the server, but one of the JSON items is an XML string that gets passed along to the XSLT processor. So I really find myself mixing and
matching based on what the best tools support for what I'm doing at the moment.
"Web Enabling the IBM i \(AS/400 and iSeries\)" <web400@xxxxxxxxxxxx> writes:
I think that today
XML is still the standard for EDI/document type of transfers in formal
webservices (SOAP)
JSON has become the standard in AJAX type of transfers from webservices
(SOA/REST)
used by browser or APP based clients.
On Fri, Jan 4, 2013 at 7:23 AM, Booth Martin <booth@xxxxxxxxxxxx> wrote:
There is a thread dated 2008, nearly 5 years ago now, discussing XML and
JSON.
Have attitudes moved in one direction or the other in that time? Is one
or the other solution becoming the de facto standard?
--
Booth Martin
802-461-5349
Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA 01376
413-676-3144
Internal: x 444
mnaughton@xxxxxxxxxxxx
****************************************
NOTICE: This e-mail and any files transmitted with it are confidential and solely for the use of the intended recipient. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that any use is
strictly prohibited. If you have received this e-mail in error, please notify us immediately by replying to it and then delete it from your computer.
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.