IETF Logo Mail Archive

Re: [httpapi] client-specified timeout?

Ben Bucksch <news@bucksch.org> Fri, 05 February 2021 23:18 UTC

Return-Path: <news@bucksch.org>
X-Original-To: httpapi@ietfa.amsl.com
Delivered-To: httpapi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CECC13A0D4D for <httpapi@ietfa.amsl.com>; Fri, 5 Feb 2021 15:18:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 Sv_f8SXZnfbv for <httpapi@ietfa.amsl.com>; Fri, 5 Feb 2021 15:18:09 -0800 (PST)
Received: from mail.server.beonex.com (mail.server.beonex.com [144.76.227.234]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DEB83A0D4B for <httpapi@ietf.org>; Fri, 5 Feb 2021 15:18:07 -0800 (PST)
To: "Salz, Rich" <rsalz@akamai.com>, "httpapi@ietf.org" <httpapi@ietf.org>
References: <7613F010-431C-47B3-802E-5258BAA5E156@akamai.com> <35f5defe-e908-d0b8-5947-bba0da6a34c8@bucksch.org> <C315C786-0160-4806-965D-E47D001D5247@akamai.com>
From: Ben Bucksch <news@bucksch.org>
Organization: Me, myself and I
Message-ID: <8981145b-bc34-4cfb-8e14-d0c5d8c0e83b@bucksch.org>
Date: Sat, 06 Feb 2021 00:18:00 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <C315C786-0160-4806-965D-E47D001D5247@akamai.com>
Content-Type: multipart/alternative; boundary="------------CF215CE7C06E0A99CFF624A5"
Content-Language: fr
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/yOIEmFng_IRPJmd12IGPIYq9lY0>
Subject: Re: [httpapi] client-specified timeout?
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/httpapi>, <mailto:httpapi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi/>
List-Post: <mailto:httpapi@ietf.org>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpapi>, <mailto:httpapi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2021 23:18:12 -0000

Am 05.02.21 um 21:47 schrieb Salz, Rich:
>
>   * Or do you mean the server should make guess whether the query will
>     take more than 300ms (possibly with the help of the database,
>     which checks how the query would look like and perform), and
>     return a failure code immediately, *without* attempting to
>     actually make the query?
>
> This.
>
> I think the “start and abort if time exceeded” is already handled, as 
> you point out.
>

Perfect. Glad for that clear answer. That makes sense.

It would be good to put that into the spec.

v2.23.0 | Report a Bug | By Email