[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: we all refer to LISTEXT as LISTEXT

To: Arnt Gulbrandsen <arnt@xxxxxxxx>
Subject: Re: we all refer to LISTEXT as LISTEXT
From: Dave Cridland <dave@xxxxxxxxxxxx>
Date: Tue, 21 Nov 2006 13:52:18 +0000
Cc: <ietf-imapext@xxxxxxx>
In-reply-to: <hqw6HDpVsNAF4+OpaZWhtQ.md5@xxxxxxxxxxxxxxxxxxx>
List-archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-id: <ietf-imapext.imc.org>
List-unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>
References: <200611211403.12916.martin.konold@xxxxxxxxxxx> <BnLUz+OOPWg2Iuae01CAug.md5@xxxxxxxxxxxxxxxxxxx> <hqw6HDpVsNAF4+OpaZWhtQ.md5@xxxxxxxxxxxxxxxxxxx>
Sender: owner-ietf-imapext@xxxxxxxxxxxx


On Tue Nov 21 13:22:01 2006, Arnt Gulbrandsen wrote:

So maybe the final RFC should name the capability LISTEXT, too. Werefer to all the other extensions by their capability name, and wedon't seem to like the name LIST-EXTENDED...

Early LISTEXTs were deployed heavily, having made it into Cyrus IMAPas an option, and then had certain Linux distributions (amongstothers) turn on the option in the binary packages.

As a result, Polymer, for example, supports both LISTEXT andLIST-EXTENDED, and encounters LISTEXT rather a lot more thanLIST-EXTENDED at the moment.


Dave.
--
Dave Cridland - mailto:dave@xxxxxxxxxxxx - xmpp:dwd@xxxxxxxxxx
 - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
 - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade

Follow-Ups:
- Re: we all refer to LISTEXT as LISTEXT
  - From: Martin Konold

References:
- we all refer to LISTEXT as LISTEXT
  - From: Arnt Gulbrandsen

Prev by Date: we all refer to LISTEXT as LISTEXT
Next by Date: Re: we all refer to LISTEXT as LISTEXT
Previous by thread: we all refer to LISTEXT as LISTEXT
Next by thread: Re: we all refer to LISTEXT as LISTEXT
Index(es):
- Date
- Thread