Return-Path: X-Original-To: apmail-falcon-dev-archive@minotaur.apache.org Delivered-To: apmail-falcon-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4497011352 for ; Thu, 24 Jul 2014 03:29:36 +0000 (UTC) Received: (qmail 28422 invoked by uid 500); 24 Jul 2014 03:29:36 -0000 Delivered-To: apmail-falcon-dev-archive@falcon.apache.org Received: (qmail 28378 invoked by uid 500); 24 Jul 2014 03:29:36 -0000 Mailing-List: contact dev-help@falcon.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@falcon.incubator.apache.org Delivered-To: mailing list dev@falcon.incubator.apache.org Received: (qmail 28361 invoked by uid 99); 24 Jul 2014 03:29:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jul 2014 03:29:35 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sriksun@hotmail.com designates 65.55.116.85 as permitted sender) Received: from [65.55.116.85] (HELO BLU004-OMC3S10.hotmail.com) (65.55.116.85) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jul 2014 03:29:32 +0000 Received: from BLU179-W5 ([65.55.116.74]) by BLU004-OMC3S10.hotmail.com with Microsoft SMTPSVC(7.5.7601.22712); Wed, 23 Jul 2014 20:29:07 -0700 X-TMN: [bLG2RiEj9XXQk8jyT2dIEflzX1mgp7Hr] X-Originating-Email: [sriksun@hotmail.com] Message-ID: Content-Type: multipart/alternative; boundary="_a9f08834-bb91-47dd-8fbb-33851747c900_" From: Srikanth Sundarrajan To: "dev@falcon.incubator.apache.org" Subject: RE: RestAPI response - can we move to MediaType.APPLICATION_JSON? Date: Thu, 24 Jul 2014 08:59:07 +0530 Importance: Normal In-Reply-To: References: ,, MIME-Version: 1.0 X-OriginalArrivalTime: 24 Jul 2014 03:29:07.0557 (UTC) FILETIME=[6D250150:01CFA6EF] X-Virus-Checked: Checked by ClamAV on apache.org --_a9f08834-bb91-47dd-8fbb-33851747c900_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Balu=2C We aren't doing anything in particular to support an addition= al mime type besides adding the annotation. Jersey is doing that for us. RegardsSrikanth Sundarrajan > Date: Wed=2C 23 Jul 2014 14:45:18 -0700 > Subject: Re: RestAPI response - can we move to MediaType.APPLICATION_JSON= ? > From: balu@hortonworks.com > To: dev@falcon.incubator.apache.org >=20 > Hi Srikanth >=20 > Sorry for the delayed response. There are no issues currently in supporti= ng > the mime types. I want to understand if there is a compelling reason for > supporting XML and JSON. If not=2C going forward we can spend fewer > resources by supporting XML or JSON. The consumer of API can easily > convert from JSON to XML or vice-versa if needed. My experience has been > that JSON is simpler to produce and maintain. >=20 > Thanks > Balu Vellanki >=20 >=20 >=20 > On Thu=2C Jul 17=2C 2014 at 11:18 PM=2C Srikanth Sundarrajan > wrote: >=20 > > Hi Balu=2C are there issues in the rest Apis supporting all the mime ty= pes? > > > > Sent from my iPhone > > > > > On 18-Jul-2014=2C at 7:18 am=2C "Balu Vellanki" > > wrote: > > > > > > Hello Team=2C > > > > > > What are the use cases or reasoning behind supporting and maintainin= g > > > MediaType.TEXT_XML=2C MediaType.TEXT_PLAIN=2C MediaType.APPLICATION_J= SON > > > responses for RestAPIs. Can we move away from XML responses and just > > > support JSON response. This would make marshalling and unmarshalling > > easier. > > > > > > Thanks > > > Balu > > > > > > -- > > > CONFIDENTIALITY NOTICE > > > NOTICE: This message is intended for the use of the individual or ent= ity > > to > > > which it is addressed and may contain information that is confidentia= l=2C > > > privileged and exempt from disclosure under applicable law. If the re= ader > > > of this message is not the intended recipient=2C you are hereby notif= ied > > that > > > any printing=2C copying=2C dissemination=2C distribution=2C disclosur= e or > > > forwarding of this communication is strictly prohibited. If you have > > > received this communication in error=2C please contact the sender > > immediately > > > and delete it from your system. Thank You. > > >=20 > --=20 > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity = to=20 > which it is addressed and may contain information that is confidential=2C= =20 > privileged and exempt from disclosure under applicable law. If the reader= =20 > of this message is not the intended recipient=2C you are hereby notified = that=20 > any printing=2C copying=2C dissemination=2C distribution=2C disclosure or= =20 > forwarding of this communication is strictly prohibited. If you have=20 > received this communication in error=2C please contact the sender immedia= tely=20 > and delete it from your system. Thank You. = --_a9f08834-bb91-47dd-8fbb-33851747c900_--