Re: NEW PREFERENCE - return=query-result
Ning Dong <ning.dong@oracle.com> Fri, 11 September 2015 19:30 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 261471B527E for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 11 Sep 2015 12:30:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.912
X-Spam-Level:
X-Spam-Status: No, score=-6.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m4Ge3RvW2EpX for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 11 Sep 2015 12:30:22 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D03C61B2DF4 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 11 Sep 2015 12:29:41 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1ZaTxY-0004g8-LR for ietf-http-wg-dist@listhub.w3.org; Fri, 11 Sep 2015 19:26:08 +0000
Resent-Message-Id: <E1ZaTxY-0004g8-LR@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <ylafon@w3.org>) id 1ZaTxT-0004fG-FM for ietf-http-wg@listhub.w3.org; Fri, 11 Sep 2015 19:26:03 +0000
Received: from raoul.w3.org ([128.30.52.128]) by lisa.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <ylafon@w3.org>) id 1ZaTxQ-00070x-6y for ietf-http-wg@w3.org; Fri, 11 Sep 2015 19:26:02 +0000
Received: from homard.platy.net ([80.67.176.7] helo=[192.168.1.36]) by raoul.w3.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <ylafon@w3.org>) id 1ZaTxP-000GFE-Nj for ietf-http-wg@w3.org; Fri, 11 Sep 2015 19:25:59 +0000
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Content-Type: text/plain; charset="us-ascii"
To: James M Snell <jasnell@gmail.com>, Phil Hunt <phil.hunt@oracle.com>
From: Ning Dong <ning.dong@oracle.com>
In-Reply-To: <CABP7RbcMTDEM6VOT7ydBTvbH0B6eTYWqVbeV6qcj-KSh7ertLw@mail.gmail.com>
Resent-From: Yves Lafon <ylafon@w3.org>
Date: Fri, 11 Sep 2015 17:34:58 +0000
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Resent-Date: Fri, 11 Sep 2015 21:25:57 +0200
Message-Id: <55F3109C.2020607@oracle.com>
X-Name-Md5: efe3dad792d606410c9cc49cedaffc94
References: <55F1FAB3.2050808@oracle.com> <44321676-D9B4-484C-A490-F5FFCE071D26@oracle.com> <CABP7RbcMTDEM6VOT7ydBTvbH0B6eTYWqVbeV6qcj-KSh7ertLw@mail.gmail.com>
Resent-To: ietf-http-wg@w3.org
X-Mailer: Apple Mail (2.2104)
X-W3C-Hub-Spam-Status: No, score=-2.4
X-W3C-Hub-Spam-Report: ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01, W3C_NW=0.5
X-W3C-Scan-Sig: lisa.w3.org 1ZaTxQ-00070x-6y 7ff159fd135a33ec07b8616c6a0f2226
X-Original-To: ietf-http-wg@w3.org
Subject: Re: NEW PREFERENCE - return=query-result
Archived-At: <http://www.w3.org/mid/55F3109C.2020607@oracle.com>
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/30198
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
Yes, that is right. We'll need two requests though: one to create the query definition resource, and one to get the result. Thanks. Ning On 9/11/2015 10:10 AM, James M Snell wrote: > To be honest, I'm entirely -1 on a preference for query-result. If > you want something like this, use PUT or POST to create the stored > query, then create a new resource that you can either use GET or > SEARCH (http://tools.ietf.org/html/draft-snell-search-method-00) on. > In my opinion, `query-result` would entirely be an abuse of the > preference mechanism. > > On Fri, Sep 11, 2015 at 8:56 AM, Phil Hunt <phil.hunt@oracle.com> wrote: >> This is difficult. Two conventions are in collision. The definition of post to create a resource and the expectation that a query returns a result. >> >> I would maybe tip the scales in favor of what most Oracle apis would need as a default. >> >> Would it be true that clients want to create stored searches by default? >> >> Phil >> >>> On Sep 10, 2015, at 14:49, Ning Dong <ning.dong@oracle.com> wrote: >>> >>> Hi, >>> Could you please review the request of adding a new value for return prefer header? >>> >>> The new value is "query-result", which is used when creating a query definition resource with POST or PUT request. >>> The client would like the server to create the query definition resource, but also execute the query and return the query result. >>> For example, >>> POST /employees/searches HTTP/1.1 >>> Host: example.org >>> Content-Type: application/json >>> Prefer: return=query-result >>> >>> { >>> "q": "name eq foo", >>> "fields": ["name","age","startdate"], >>> "orderBy": ["name","age:desc"] >>> } >>> >>> This above resource defines a query (equivalent to select name, age, startdate from employees where employees.name='foo' order by name, age desc). >>> Without the Prefer: return=query-result header, the server would just create a new resource and return a 201 response. >>> If server honors the prefer header, then the server will not only create a new resource, but also execute the query based on the query definition. >>> The response body will contain the result of the query execution, such as: >>> 201 Created >>> Preference-Applied: return=query-result >>> Location: http://example.com/employees/searches/q1 >>> Content-Location: http://example.com/employees/searches/q1/result >>> >>> { >>> "items": [ >>> {"name": "foo", >>> "age": 35, >>> "startdate": "2008-02-15"} >>> ] >>> } >>> >>> o Preference: return >>> >>> o Value: query-result >>> >>> o Optional Parameters: n/a >>> >>> o Description: It is used to indicate that result of the query execution is preferred in the response. >>> >>> o Reference: Oracle will add a new sub type (type=query-def) in application/vnd.oracle.resource+json media type. This new sub type uses return=query-result prefer header. >>> The application/vnd.oracle.resource+json media type is defined at: >>> http://www.oracle.com/webfolder/technetwork/tutorials/appdevinfo/New%20REST%20Media%20Type.pdf >>> >>> o Notes: It is related to another request to add "transient" prefer header. >>> >>> >>> Thanks and appreciate your review. >>> >>> >>> Ning >>> >>> >>> >>>
- NEW PREFERENCE - return=query-result Ning Dong
- Re: NEW PREFERENCE - return=query-result Phil Hunt
- Re: [Moderator Action] NEW PREFERENCE - return=qu… Ning Dong
- Re: NEW PREFERENCE - return=query-result James M Snell
- Re: NEW PREFERENCE - return=query-result Ning Dong
- Re: NEW PREFERENCE - return=query-result Phil Hunt
- Re: NEW PREFERENCE - return=query-result Matthew Kerwin
- Re: NEW PREFERENCE - return=query-result Phil Hunt
- Re: NEW PREFERENCE - return=query-result Matthew Kerwin
- Re: NEW PREFERENCE - return=query-result Phil Hunt
- Re: NEW PREFERENCE - return=query-result Matthew Kerwin
- Re: NEW PREFERENCE - return=query-result James M Snell
- Re: NEW PREFERENCE - return=query-result Ning Dong
- Re: NEW PREFERENCE - return=query-result Ning Dong