Re: [dispatch] A WG for HTTP API Building Blocks

Anton Tveretin <tveretinas@yandex.ru> Thu, 16 July 2020 16:39 UTC

Return-Path: <tveretinas@yandex.ru>
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 A599F3A0C13 for <dispatch@ietfa.amsl.com>; Thu, 16 Jul 2020 09:39:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.279
X-Spam-Level:
X-Spam-Status: No, score=0.279 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=yandex.ru
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 EAq0C7IlCV24 for <dispatch@ietfa.amsl.com>; Thu, 16 Jul 2020 09:39:22 -0700 (PDT)
Received: from forward105j.mail.yandex.net (forward105j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::108]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8B2C3A0C15 for <dispatch@ietf.org>; Thu, 16 Jul 2020 09:39:21 -0700 (PDT)
Received: from forward102q.mail.yandex.net (forward102q.mail.yandex.net [IPv6:2a02:6b8:c0e:1ba:0:640:516:4e7d]) by forward105j.mail.yandex.net (Yandex) with ESMTP id 2A319B216A7 for <dispatch@ietf.org>; Thu, 16 Jul 2020 19:32:16 +0300 (MSK)
Received: from mxback3q.mail.yandex.net (mxback3q.mail.yandex.net [IPv6:2a02:6b8:c0e:39:0:640:4545:437c]) by forward102q.mail.yandex.net (Yandex) with ESMTP id 22A157F20025 for <dispatch@ietf.org>; Thu, 16 Jul 2020 19:32:16 +0300 (MSK)
Received: from localhost (localhost [::1]) by mxback3q.mail.yandex.net (mxback/Yandex) with ESMTP id IFFUDIP7f8-WFHKi5lW; Thu, 16 Jul 2020 19:32:15 +0300
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1594917135; bh=VPVa8hkdkQICV+z4fS6+9RfDdvbqcKfghWelQqmE4fw=; h=Message-Id:Date:Subject:To:From; b=d6UotrdE3Ahs1Y1FQryL8rLQf71LZkIqLvoZaJocqXxZIo1c6nB9Bo2RZkXbr0OKd /oD0cMVoxTi68W8Fs54iPUKD446G5wBIwgkVVJoxvElnMHKtmUmsawXipWYUJ2XbOc Mac7lTtl7c6uuuOmyj+gxEgZrUf7Lj7bC+XI9IvQ=
Authentication-Results: mxback3q.mail.yandex.net; dkim=pass header.i=@yandex.ru
Received: by vla5-b4d100574cfc.qloud-c.yandex.net with HTTP; Thu, 16 Jul 2020 19:32:15 +0300
From: Anton Tveretin <tveretinas@yandex.ru>
To: DISPATCH list <dispatch@ietf.org>
MIME-Version: 1.0
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Date: Thu, 16 Jul 2020 21:32:15 +0500
Message-Id: <5127121594916975@mail.yandex.ru>
Content-Transfer-Encoding: 7bit
Content-Type: text/html
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/Ir87feBdQfO21VjL475ADb2XcAk>
Subject: Re: [dispatch] A WG for HTTP API Building Blocks
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: Thu, 16 Jul 2020 16:39:24 -0000

Hello,
Of HTTP APIs, I know XMLHTTPRequest. Is it unsufficient?
And I think there are no common server-side APIs, only server (implementation) specific.
Sincerely yours.