Return-Path: Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: (qmail 86914 invoked from network); 12 Mar 2009 16:43:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Mar 2009 16:43:35 -0000 Received: (qmail 95471 invoked by uid 500); 12 Mar 2009 16:43:34 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 95437 invoked by uid 500); 12 Mar 2009 16:43:34 -0000 Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list dev@cxf.apache.org Received: (qmail 95426 invoked by uid 99); 12 Mar 2009 16:43:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Mar 2009 09:43:34 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [192.77.186.17] (HELO mx3.progress.com) (192.77.186.17) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Mar 2009 16:43:26 +0000 Received: from mx3.progress.com (127.0.0.1) by mx3.progress.com (MlfMTA v3.2r9) id hn4tqs0171s2 for ; Thu, 12 Mar 2009 12:43:05 -0400 (envelope-from ) Received: from progress.com ([192.233.92.16]) by mx3.progress.com (SonicWALL 6.2.2.1073) with ESMTP; Thu, 12 Mar 2009 12:43:05 -0400 Received: from NTEXFE01.bedford.progress.com (ntexfe01 [10.128.10.24]) by progress.com (8.13.8/8.13.8) with ESMTP id n2CGgxDE019757 for ; Thu, 12 Mar 2009 12:42:59 -0400 (EDT) Received: from sberyoz ([10.5.2.12]) by NTEXFE01.bedford.progress.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Thu, 12 Mar 2009 12:42:58 -0400 Message-ID: <001e01c9a331$991ba2e0$0c02050a@emea.progress.com> From: "Sergey Beryozkin" To: References: <01eb01c9a326$a1226380$0c02050a@emea.progress.com> Subject: Re: Multiple HTTP methods per method in JAXRS (Re: Possibly retarded question) Date: Thu, 12 Mar 2009 16:42:55 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-OriginalArrivalTime: 12 Mar 2009 16:42:59.0112 (UTC) FILETIME=[9A1D8280:01C9A331] X-Mlf-Version: 6.2.2.1073 X-Mlf-UniqueId: o200903121642590294783 X-Virus-Checked: Checked by ClamAV on apache.org > > Don't make Roy Fielding have to come around to your house! This is funny :-) > I think if you use GET and POST on the same URI then you are > innappropriately 'crossing the streams' and making it ambiguous > as to whether the invocation is idempotent or not. That is true. That said, one way of looking at having say both GET and POST at the same method is that a user is saying : I know that some new clients call GET and while others (legacy ones) call POST (with POST clients in this example providing an unexpected HTTP method), which I reckon what Gary is after in this case. Typically users write filters to do it or provide multiple methods delegating to a common one. Supporting multiple HTTP methods on a single method would be just another way to achieve the same fairly specific goal. Cheers, Sergey ----- Original Message ----- From: "Oisin Hurley" To: Sent: Thursday, March 12, 2009 4:12 PM Subject: Re: Multiple HTTP methods per method in JAXRS (Re: Possibly retarded question) >> I don't think it's a bad idea per se. JAXRS does not prohibit multiple >> annotations per se (AFAIK), it's just undefined what happens. > > I think if you use GET and POST on the same URI then you are > innappropriately 'crossing the streams' and making it ambiguous > as to whether the invocation is idempotent or not. > > Don't make Roy Fielding have to come around to your house! > > --oh