XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] json v. xml

On Thu, 04 Jan 2007 12:58:16 -0500, derek denny-brown <zuligag@gmail.com>  
wrote:

> These questions seem to be falling into the same trap that Dare
> complained about.  JSON is a simple single solution to a whole set of
> problems.  It addresses cross-domain access.  It is fast.  It is easy
> to use.  On every account, XML fares worse.

Yep. I aknowledged that. It does not work for my needs.

I even went so far as creating a JS version of cached SAX events for the  
(deeply) nested JSON object(s). I even tried to create a transformation  
object for it. I couldn't figure out how to do it. Probably someone can. I  
am just asking questions :)

-Rob



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS