draft-ietf-imapext-thread
Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Tue, 29 May 2001 20:36 UTC
Received: by above.proper.com (8.9.3/8.9.3) id NAA11273 for ietf-imapext-bks; Tue, 29 May 2001 13:36:22 -0700 (PDT)
Received: from melkebalanse.troll.no (bluegrass.camelot.de [217.19.165.66]) by above.proper.com (8.9.3/8.9.3) with ESMTP id NAA11254 for <ietf-imapext@imc.org>; Tue, 29 May 2001 13:36:12 -0700 (PDT)
Received: (from arnt@localhost) by melkebalanse.troll.no (8.9.3/8.8.5) id WAA26615; Tue, 29 May 2001 22:35:43 +0200
Date: Tue, 29 May 2001 22:35:43 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: ietf-imapext@imc.org
Subject: draft-ietf-imapext-thread
Message-ID: <20010529223543.E26574@melkebalanse.troll.no>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Sender: owner-ietf-imapext@mail.imc.org
Precedence: bulk
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>
The thread extension offers no way to get threading information for only some mail (typically, the newly arrived messages). Isn't this a problem? The thread=references model specifies an algorithm to be used, in detail, and that algorithm is one that makes several passes over the entire set of messages. The algorithm is complex, and it's not clear to me whether it can be adapted to be incremental without possibly changing its output, and whether such changes are permitted by the draft. So, if a server does incremental References:-based threading on delivery, can it advertise thread=references? --Arnt
- Re: draft-ietf-imapext-thread Mark Crispin
- Re: draft-ietf-imapext-thread Arnt Gulbrandsen
- re: draft-ietf-imapext-thread Mark Crispin
- draft-ietf-imapext-thread Arnt Gulbrandsen
- Re: draft-ietf-imapext-thread Mark Crispin
- Re: draft-ietf-imapext-thread Arnt Gulbrandsen
- Re: draft-ietf-imapext-thread Cyrus Daboo
- Re: draft-ietf-imapext-thread Arnt Gulbrandsen
- Re: draft-ietf-imapext-thread Ken Murchison
- Re: draft-ietf-imapext-thread Arnt Gulbrandsen
- Re: draft-ietf-imapext-thread Ken Murchison