Re: XML and JSON

["Alfredo Delgado" <adelgado@xxxxxxxxxxxxxxxxx>]

This example isn't really AJAX but it's using JDE address book data out of
DB2 to be utilized in JavaScript. XML would have also worked.

1. There's a SQL query.
2. I wrote what I consider to be an ad hoc JSON view of the data in PHP. (
http://www.lairdplastics.com/locations/dsp_GetBusinessUnits.js.php)
3. That data structure is included as external JS source along with the
Google Maps API here: http://www.lairdplastics.com/content/section/4/39/
4. Same query, different view:
http://www.lairdplastics.com/content/section/16/55/

On Mon, Apr 28, 2008 at 2:01 PM, Maurice O'Prey <maurice.oprey@xxxxxxxxx>
wrote:

> Would it be too much to ask for a description of a 'real world'
> implementation of JSON, one where XML and web services would not fit nor
> perform very well?
>
> I don't doubt the usefulness of JSON, I just need to learn by example (and
> learn to live within standards)
>
> Maurice O'Prey
>
>
> -----Original Message-----
> From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
> Behalf Of Joe Pluta
> Sent: 28 April 2008 18:21
> To: Web Enabling the AS400 / iSeries
> Subject: Re: [WEB400] XML and JSON
>
> Walden H. Leverich wrote:
> > If this is a true webservice with WSDL and all that, than the payloads
> > are XML, and usually with children not attributes. As Joe mentioned,
> > it's definitely "efficiency challenged" (nice phrase), but it's also the
> > simplest, and there's something to be said for simplicity when working
> > between machines and technologies.
> >
> > If the response is for an Ajax request then we go the JSON approach. Not
> > only because the size is (typically) smaller, but because it's really
> > nice to be able to rehydrate a complete object graph on the browser with
> > a simple eval statement (or in our case Prototype's
> > Ajax.Response.responseJSON property)
> I don't know that I call SOAP simpler than JSON, but it's more
> standardized, I guess.  It's just that the majority of the standarized
> junk is pretty useless in many circumstances, primarily the Ajax type of
> request.  As Walden points out, JSON is designed specifically for quick
> movement of data between machines - structures on the wire.  This is the
> part that I've had to rewrite so many times over the years, and its
> amazing how little work it is with JSON.
>
> Joe
> --
> 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.
>
> --
> 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.