Comments on: JSON Pros and Cons http://myarch.com/json-pros-and-cons Builds and bytes Wed, 17 Mar 2010 11:08:26 -0400 http://wordpress.org/?v=2.8.4 hourly 1 By: ANURAG SHARAN http://myarch.com/json-pros-and-cons/comment-page-1#comment-35213 ANURAG SHARAN Sun, 28 Feb 2010 15:26:24 +0000 http://myarch.com/json-pros-and-cons#comment-35213 EXCELLENT BASICS MATERIAL.. GOOD STUFF FOR BEGINNERS EXCELLENT BASICS MATERIAL.. GOOD STUFF FOR BEGINNERS

]]> By: Prashant Joshi http://myarch.com/json-pros-and-cons/comment-page-1#comment-34814 Prashant Joshi Thu, 18 Dec 2008 15:10:18 +0000 http://myarch.com/json-pros-and-cons#comment-34814 Every technology has its own merits and de-merits. As per my experience, JSON is good for sending small information over http. when use along with REST, it offers lots of flexibility, specially when working in cross technology domain. Every technology has its own merits and de-merits. As per my experience, JSON is good for sending small information over http. when use along with REST, it offers lots of flexibility, specially when working in cross technology domain.

]]> By: Sharath http://myarch.com/json-pros-and-cons/comment-page-1#comment-24355 Sharath Mon, 10 Mar 2008 19:01:36 +0000 http://myarch.com/json-pros-and-cons#comment-24355 Does Json webservice allow List or arrays having more elements within them as members of a return type List Does Json webservice allow List or arrays having more elements within them as members of a return type List

]]> By: » JSON Web Services - the XML JSON debate further ahead TechTracer: Tracing the course of technology http://myarch.com/json-pros-and-cons/comment-page-1#comment-6020 » JSON Web Services - the XML JSON debate further ahead TechTracer: Tracing the course of technology Sun, 01 Apr 2007 13:52:26 +0000 http://myarch.com/json-pros-and-cons#comment-6020 [...] JSON- Some Facts Coming back to JSON, the main fact which goes against JSON is it is not standardized. But now if JSON wants to establish its presence then the only field in my opinion would be SOA web services and AJAX where, it has received a lot of attention. Lately the debate on using web services with JSON has started. XML being heavy puts somewhat a hindrance on the acceptance of web services since the network infrastructure needs to get upgraded to get quicker adoption of XML RPC web services. With JSON, if web services give a higher throughput then it might be time to cash upon its acceptance for data transfer. Alexander writes about JSON pros and cons in his blog MyArch, One of the keys to SOA success is that it should be easy to consume a service, i.e., the entry barrier for service consumers must be low to support “grass root” SOA adoption. While a top-down SOA effort may succeed, it will certainly take longer than bottom-up (”grass-root”) approach when developers are able to consume services as they see fit. AJAX/JSON fits this bill perfectly - it is easily understood by developers and it does not require any Web services -specific tools or infrastructure.So overall I’m pretty enthusiastic about JSON. [...] [...] JSON- Some Facts Coming back to JSON, the main fact which goes against JSON is it is not standardized. But now if JSON wants to establish its presence then the only field in my opinion would be SOA web services and AJAX where, it has received a lot of attention. Lately the debate on using web services with JSON has started. XML being heavy puts somewhat a hindrance on the acceptance of web services since the network infrastructure needs to get upgraded to get quicker adoption of XML RPC web services. With JSON, if web services give a higher throughput then it might be time to cash upon its acceptance for data transfer. Alexander writes about JSON pros and cons in his blog MyArch, One of the keys to SOA success is that it should be easy to consume a service, i.e., the entry barrier for service consumers must be low to support “grass root” SOA adoption. While a top-down SOA effort may succeed, it will certainly take longer than bottom-up (”grass-root”) approach when developers are able to consume services as they see fit. AJAX/JSON fits this bill perfectly – it is easily understood by developers and it does not require any Web services -specific tools or infrastructure.So overall I’m pretty enthusiastic about JSON. [...]

]]> By: Alexander Ananiev http://myarch.com/json-pros-and-cons/comment-page-1#comment-4658 Alexander Ananiev Thu, 15 Feb 2007 14:11:29 +0000 http://myarch.com/json-pros-and-cons#comment-4658 Raymond: JSON is indeed language independent, however, the balance shifts when you are not using JavaScript - most other languages have very good Web services and XML support, so I'm not sure what would be the use case for JSON, say, in .NET or Java environment. It's the lack of good XML support in browsers that makes JSON so appealing IMO. Raymond:
JSON is indeed language independent, however, the balance shifts when you are not using JavaScript – most other languages have very good Web services and XML support, so I’m not sure what would be the use case for JSON, say, in .NET or Java environment. It’s the lack of good XML support in browsers that makes JSON so appealing IMO.

]]> By: Raymond http://myarch.com/json-pros-and-cons/comment-page-1#comment-4650 Raymond Thu, 15 Feb 2007 04:52:56 +0000 http://myarch.com/json-pros-and-cons#comment-4650 The comparison gave the impression that JSON can only be used with Javascript. According the author, he defined JSON using javascript but it is a standard that is not confined to Javascript. It is "...a" text format that is completely language independent." Go to www.JSON.org and read about JSON. Also there are links that answers some of the issues raised in this article. I am not for or against JSON. XML and JSON both has their own merits. A good developer will pick the best to use for the situation. The comparison gave the impression that JSON can only be used with Javascript.
According the author, he defined JSON using javascript but it is a standard that is not confined to Javascript. It is “…a” text format that is completely language independent.”

Go to http://www.JSON.org and read about JSON. Also there are links that answers some of the issues raised in this article.

I am not for or against JSON. XML and JSON both has their own merits. A good developer will pick the best to use for the situation.

]]> By: Hans http://myarch.com/json-pros-and-cons/comment-page-1#comment-4643 Hans Wed, 14 Feb 2007 18:11:37 +0000 http://myarch.com/json-pros-and-cons#comment-4643 I've been wondering about what acronym should be used for "Asynchronous JavaScript and JSON". But if you write it all out you get "Asynchronous JavaScript and JavaScript Object Notation", so "JavaScript" is redundant and the phrase can be shortened to "Asynchronous JavaScript Object Notation". AJON? Thanks for the writeup! I’ve been wondering about what acronym should be used for “Asynchronous JavaScript and JSON”. But if you write it all out you get “Asynchronous JavaScript and JavaScript Object Notation”, so “JavaScript” is redundant and the phrase can be shortened to “Asynchronous JavaScript Object Notation”. AJON?

Thanks for the writeup!

]]> By: nhm tanveer hossain khan (hasan) http://myarch.com/json-pros-and-cons/comment-page-1#comment-4624 nhm tanveer hossain khan (hasan) Wed, 14 Feb 2007 03:36:53 +0000 http://myarch.com/json-pros-and-cons#comment-4624 JSON is promising, comparing xml or more complex xml content like soap, json saves a lot of processing pressure. it is a great recuse for the visitor. JSON is promising, comparing xml or more complex xml content like soap, json saves a lot of processing pressure. it is a great recuse for the visitor.

]]>