IMAP4 Connection Management
draft-karppinen-imap-conman-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Marko Karppinen , Andrew Skalski | ||
| Last updated | 1999-10-05 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The IMAP4 [RFC-2060] protocol is based on the client-server paradigm where a single client is concerned only with the mail of a single user. However, due to advent of several scenarios where n-tier interaction is desired, the need has arisen to work with several users' mail during a single IMAP4 connection. In such scenario, a component of a n-tier system may act as an IMAP4 client on behalf of multiple end-users. Present examples of this include many WWW-based email services. Initial profiling suggests that persistent IMAP4 connections can lead to a performance increase of an order of magnitude when compared to separate IMAP4 connections per mailbox action. This document defines an extension to the IMAP4 protocol that allows a persistent connection to be established for accessing the mail of multiple users. The extension includes a new USERLOGOUT command, and a requirement for a CAPABILITIES response from servers implementing the extension.
Authors
Marko Karppinen
Andrew Skalski
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)