IETF Logo Mail Archive

Re: [imapext] Fwd: About connection pooling

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Sun, 27 September 2020 14:22 UTC

Return-Path: <arnt@gulbrandsen.priv.no>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 812CC3A0FA9 for <imapext@ietfa.amsl.com>; Sun, 27 Sep 2020 07:22:48 -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, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gulbrandsen.priv.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 Qt3RDBzZnVEU for <imapext@ietfa.amsl.com>; Sun, 27 Sep 2020 07:22:47 -0700 (PDT)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [144.76.73.169]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D61243A0F8C for <imapext@ietf.org>; Sun, 27 Sep 2020 07:22:46 -0700 (PDT)
Received: from stabil.gulbrandsen.priv.no (stabil.gulbrandsen.priv.no [IPv6:2a01:4f8:191:91a8::3]) by stabil.gulbrandsen.priv.no (Postfix) with ESMTP id 52F9DC014F; Sun, 27 Sep 2020 15:28:53 +0100 (IST)
Authentication-Results: stabil.gulbrandsen.priv.no; dmarc=none (p=none dis=none) header.from=gulbrandsen.priv.no
Authentication-Results: stabil.gulbrandsen.priv.no; spf=none smtp.mailfrom=arnt@gulbrandsen.priv.no
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gulbrandsen.priv.no; s=mail; t=1601216933; bh=g8OCL1MnsueBuS1WPiwWFiFTML2W+o/fE3odlTP4cmQ=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=Nn0k9NE+JVRyh6HFXYkAyO3EjMOQeED/2zcHhxaHYZOzb4y+h41p1TbIreot5LdyS zx8TKtEqloF7CqMsGaWKFPv1d7HXXN3pdGECPG5FUWUDa0LHWwlpVf5HD4z5UcXLKY uZfmh6uHmnNMWC/6vb5XmDbkWDuvaOdKwFB7GpXU=
Received: from arnt@gulbrandsen.priv.no by stabil.gulbrandsen.priv.no (Archiveopteryx 3.2.0) with esmtpsa id 1601216932-28651-19140/9/1; Sun, 27 Sep 2020 14:28:52 +0000
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: Rohan Mehta <rohanmehta0077@gmail.com>
Cc: imapext@ietf.org
Date: Sun, 27 Sep 2020 16:31:25 +0200
Mime-Version: 1.0
Message-Id: <f53b4661-1d6c-4243-b76d-169ba1a33017@gulbrandsen.priv.no>
In-Reply-To: <CAO0d3bJ_ma7R+0Xti0sO8fEL9g1qJWfs8F25O7GODT2r4eEzaQ@mail.gmail.com>
References: <CAO0d3bLXzYynT-9BxDy2DS4nHGzVM2hBTAQyyy2nhu-s1FmsNg@mail.gmail.com> <CAO0d3bJ_ma7R+0Xti0sO8fEL9g1qJWfs8F25O7GODT2r4eEzaQ@mail.gmail.com>
User-Agent: Trojita/0.7; Qt/5.11.3; xcb; Linux; Devuan GNU/Linux 3 (beowulf)
Content-Type: text/plain; charset="utf-8"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/imapext/wo53XrZ1HUzqoJbblm4rG9-XRLI>
Subject: Re: [imapext] Fwd: About connection pooling
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Sep 2020 14:22:52 -0000

Connection pooling isn't in the protocol because it adds complexity and 
doesn't save significant resources.

IMAP says: Starting at successful login, all commands on a connection use 
the credentials of a single user. That's a simple model.

It simplifies the protcol and some server implementations. A server that 
wishes to process commands for several users can accept commands on several 
connections and get effectively the same resource usage as it would get by 
using a single connection.

Arnt

v2.23.0 | Report a Bug | By Email