IETF Logo Mail Archive

Re: [dispatch] Building Blocks for HTTP APIs - next steps

Rob Sayre <sayrer@gmail.com> Wed, 05 August 2020 05:10 UTC

Return-Path: <sayrer@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E8943A0B3A for <dispatch@ietfa.amsl.com>; Tue, 4 Aug 2020 22:10:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 BheWNAAO2Nbb for <dispatch@ietfa.amsl.com>; Tue, 4 Aug 2020 22:10:04 -0700 (PDT)
Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E441B3A0B38 for <dispatch@ietf.org>; Tue, 4 Aug 2020 22:10:03 -0700 (PDT)
Received: by mail-io1-xd2e.google.com with SMTP id a5so29373023ioa.13 for <dispatch@ietf.org>; Tue, 04 Aug 2020 22:10:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Cd25bFF36OB1uINhNlAvbCNgBWdliynWepGSet+gAY4=; b=hJKwgacZuE32pLzYPk6FHEAeZKBw3bkLFNDcKuLF7a9Wm1RkySEcln0+dy8uSuZ04a jRH7LxpTKtkg/Erz7s+x5HKqY48h8ceiussOtqvxGOyvbzdTEjHhghuYzQ6Ke9wXIL48 xbW/SelSp8xYwyBC2RKtOuz4rfVRsb8xh7EEMUEdFJdL0Hsf2F7YYiNOpui++EbYWdog UAkFk1so1H78EUkMbEsCpL+av9AHqHTvh3JF9ZQNtuG6Jx9wk/eoXne08K8byc9j82gG QZDIgQiCAFajHLW1HBLv3g3AWrQD3/kIDX6nHjmvsQBJptZnBn5nxMzEr91KgcpPZDt8 5GGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Cd25bFF36OB1uINhNlAvbCNgBWdliynWepGSet+gAY4=; b=b83szMSPcrZnrhg7ZHqIwF2RRDSviaXc5GZLFYsggweIHrg5Wlz71DgLsudmE2d4uz AqyqnOVMzGPGW9nAVUrEGg2CttnDlIItrYEzp2xPazXY484SpTBCpaSlNZB4CcLKYqWu gCAGyiOcUQZq6ptYrB/xXciaPmdRU7ep7tMLXpicl9Md0pNkCoLDDwfwvWeKkkYDvL9Z mG7P3nG9lAt8L6qTvwbTsCVPHnDZ06Is4GM9UlPmOCLVQWjX7dP9OXePDcYQ8GG06YUN /qwBKe6H9w1bIu+Wt0nnAbbW0Hnuu4hukG8B3y1KTDuDAAzyJLsAwk28kdJ79skgDZAf Q9Zg==
X-Gm-Message-State: AOAM530guIoCd2QZRuTfsiiz1fd/1SCOSGvTycroVZJ0GFC8ehlJy9SC bLUFHoa1w9SSpZ/D4kyx3Pynen8sN6VSYPQIN+E=
X-Google-Smtp-Source: ABdhPJw3RLiWA3qFT3P9ptos/7OON/zBLPO8W2+BZrH09PSZH25AwvewvZauRwE2+wTBMEFHOc2irJT65Q/tAn9ACFo=
X-Received: by 2002:a05:6602:2417:: with SMTP id s23mr1544090ioa.94.1596604203053; Tue, 04 Aug 2020 22:10:03 -0700 (PDT)
MIME-Version: 1.0
References: <FED20ECD-A850-407E-B0DE-59A43B8D318E@mnot.net> <CAChr6SxUj07PRfKVi6V7APFGyh3Hv9ifRuXbYba8N8KzX1iv6Q@mail.gmail.com> <CH2PR00MB084497EEB38BC0EFED683165F04C0@CH2PR00MB0844.namprd00.prod.outlook.com>
In-Reply-To: <CH2PR00MB084497EEB38BC0EFED683165F04C0@CH2PR00MB0844.namprd00.prod.outlook.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Tue, 04 Aug 2020 22:09:48 -0700
Message-ID: <CAChr6SzH8djH1gS1rF8nBJbbc_kD7Va5XxO4+22G0sN_M4Hmiw@mail.gmail.com>
To: Darrel Miller <Darrel.Miller@microsoft.com>
Cc: Mark Nottingham <mnot@mnot.net>, DISPATCH WG <dispatch@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005eb6a105ac1a62c1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/0AT4oeBKqFA0Ryf1fgRzRqu4uUs>
Subject: Re: [dispatch] Building Blocks for HTTP APIs - next steps
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Aug 2020 05:10:05 -0000

On Sat, Aug 1, 2020 at 8:18 PM Darrel Miller <Darrel.Miller@microsoft.com>
wrote:

> Hi Rob,
>
>
>
> There is a sub group within the Linux Foundation GraphQL project that is
> focused on creating a specification of how GraphQL should be layered on
> HTTP.
> https://github.com/graphql/graphql-over-http/blob/master/spec/GraphQLOverHTTP.md
>
>
>
> I think the HTTP API Working group could co-ordinate with that group to
> identify any gaps in HTTP conventions/patterns or guidance that would help
> with GraphQL layering over HTTP.
>
>
>
> From the perspective of HTTP, GraphQL is media type for the query and one
> for the schema.  The response is application/json...
>

I don't agree. The reference implementations of GraphQL expect
application/json, but higher-traffic services do not tend to use that
format. See: https://spec.graphql.org/June2018/#sec-Serialization-Format

While this is not an objection, I think the WG might want to avoid defining
APIs in terms of links and JSON, when that is becoming a less common tactic.

thanks,
Rob

v2.23.0 | Report a Bug | By Email