IETF Logo Mail Archive

Re: [httpapi] client-specified timeout?

"Salz, Rich" <rsalz@akamai.com> Fri, 05 February 2021 20:47 UTC

Return-Path: <rsalz@akamai.com>
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 05CB13A0813 for <httpapi@ietfa.amsl.com>; Fri, 5 Feb 2021 12:47:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.348
X-Spam-Level:
X-Spam-Status: No, score=-2.348 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=akamai.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 onTxDOw59GM1 for <httpapi@ietfa.amsl.com>; Fri, 5 Feb 2021 12:47:24 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52D673A0812 for <httpapi@ietf.org>; Fri, 5 Feb 2021 12:47:24 -0800 (PST)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.43/8.16.0.43) with SMTP id 115KePWE022825; Fri, 5 Feb 2021 20:47:17 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=ez9QAL7cUM6qhqIPpH6zFcivQEglIDf8KyfnaGphTDg=; b=CxzKUw9HMPH0n3uvAlNNGu83HVkbGlBV2W9XAXNVpt/VJAmJz71K/oCaa/nB/4gN9em1 X+ELe0zfRx+ozmRbLJLpiv8ug49vFuCTNsu4JfDN2313OBSDd2WSMOWohj5GyPtU1mwu rrq0HOsOe8HBScsk/ZV3NpPf4v2ORJth6XVlXEeHo1S6+3wQIFKp7yQpW7vAvOB/fJU3 3aFN26IGotG/2H3p89MNzH3Kx7b6fTttgNtxd9N4zbKJKET/zr+ls9Mho0/IV/jBPmSl ySybOqejPYa2XHzGIvuGkKGTrpTnsN5GuREZt8twyKq4i6/+z81o5SLwlDYBWD9lCfbR AQ==
Received: from prod-mail-ppoint3 (a72-247-45-31.deploy.static.akamaitechnologies.com [72.247.45.31] (may be forged)) by m0050102.ppops.net-00190b01. with ESMTP id 36d0k1txxj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 05 Feb 2021 20:47:17 +0000
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.43/8.16.0.43) with SMTP id 115KZfKR031656; Fri, 5 Feb 2021 15:47:16 -0500
Received: from email.msg.corp.akamai.com ([172.27.165.113]) by prod-mail-ppoint3.akamai.com with ESMTP id 36d3p4ssw6-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Fri, 05 Feb 2021 15:47:16 -0500
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.165.119) by ustx2ex-dag1mb1.msg.corp.akamai.com (172.27.165.119) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 5 Feb 2021 14:47:15 -0600
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com ([172.27.165.119]) by ustx2ex-dag1mb1.msg.corp.akamai.com ([172.27.165.119]) with mapi id 15.00.1497.010; Fri, 5 Feb 2021 14:47:15 -0600
From: "Salz, Rich" <rsalz@akamai.com>
To: Ben Bucksch <news@bucksch.org>, "httpapi@ietf.org" <httpapi@ietf.org>
Thread-Topic: [httpapi] client-specified timeout?
Thread-Index: AQHW+/BTluM3M+wTdkuU+jT2kk+MZKpKakoA//+uwwA=
Date: Fri, 05 Feb 2021 20:47:14 +0000
Message-ID: <C315C786-0160-4806-965D-E47D001D5247@akamai.com>
References: <7613F010-431C-47B3-802E-5258BAA5E156@akamai.com> <35f5defe-e908-d0b8-5947-bba0da6a34c8@bucksch.org>
In-Reply-To: <35f5defe-e908-d0b8-5947-bba0da6a34c8@bucksch.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.45.21011103
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.164.43]
Content-Type: multipart/alternative; boundary="_000_C315C78601604806965DE47D001D5247akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.737 definitions=2021-02-05_11:2021-02-05, 2021-02-05 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 malwarescore=0 mlxlogscore=994 adultscore=0 suspectscore=0 bulkscore=0 phishscore=0 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2102050128
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.737 definitions=2021-02-05_11:2021-02-05, 2021-02-05 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 malwarescore=0 lowpriorityscore=0 impostorscore=0 mlxscore=0 suspectscore=0 clxscore=1015 bulkscore=0 phishscore=0 spamscore=0 mlxlogscore=908 adultscore=0 priorityscore=1501 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2009150000 definitions=main-2102050129
X-Agari-Authentication-Results: mx.akamai.com; spf=${SPFResult} (sender IP is 72.247.45.31) smtp.mailfrom=rsalz@akamai.com smtp.helo=prod-mail-ppoint3
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/rpwhOY2KqO-i0-i067v8ZKnOgKo>
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 20:47:26 -0000

  *   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.

v2.23.0 | Report a Bug | By Email