IETF Logo Mail Archive

Re: draft-ietf-imapext-thread

Arnt Gulbrandsen <arnt@gulbrandsen.priv.no> Wed, 13 June 2001 16:20 UTC

Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.3/8.11.3) id f5DGKEh28044 for ietf-imapext-bks; Wed, 13 Jun 2001 09:20:14 -0700 (PDT)
Received: from melkebalanse.troll.no (bluegrass.camelot.de [217.19.165.66]) by above.proper.com (8.11.3/8.11.3) with ESMTP id f5DGKCJ28040 for <ietf-imapext@imc.org>; Wed, 13 Jun 2001 09:20:12 -0700 (PDT)
Received: (from arnt@localhost) by melkebalanse.troll.no (8.9.3/8.8.5) id SAA03173; Wed, 13 Jun 2001 18:26:08 +0200
Date: Wed, 13 Jun 2001 18:26:08 +0200
From: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
To: Cyrus Daboo <daboo@cyrusoft.com>
Cc: Ken Murchison <ken@oceana.com>, Mark Crispin <MRC@cac.washington.edu>, ietf-imapext@imc.org
Subject: Re: draft-ietf-imapext-thread
Message-ID: <20010613182608.C3158@melkebalanse.troll.no>
References: <20010529223543.E26574@melkebalanse.troll.no> <MailManager.991169858.2809.mrc@Tomobiki-Cho.CAC.Washington.EDU> <20010530111859.A26726@melkebalanse.troll.no> <3B26CE21.415319DE@oceana.com> <20010613104824.C2664@melkebalanse.troll.no> <3B276AF6.DCFCBE01@oceana.com> <20010613155007.B2860@melkebalanse.troll.no> <40530000.992443727@euphrates.cyrusoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <40530000.992443727@euphrates.cyrusoft.com>
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>

Cyrus Daboo <daboo@cyrusoft.com>
> --On Wednesday, June 13, 2001 03:50:07 PM +0200 Arnt Gulbrandsen 
> <arnt@gulbrandsen.priv.no> wrote:
> 
> >> It can't because the unseen search takes place BEFORE the threading.
> >
> > The answer sounds like putting the cart before the horse... _why_ does
> > the search take place before threading?
> 
> You need to think about this as two different actions (I've actually 
> written some of this up in the ficticious WINDOW draft which I hope to get 
> out soon):

I've been looking forward to reading that, actually.

> There are two types of 'windowing' mode: input windowing and output 
> windowing.
...

I can understand that. However, I get the impression that input windowing
in the case of THREAD isn't considered very useful. Is that right?

With output windowing, THREAD would be a sort of "SEARCH, and give me
context for the results, and give me the results in the right order"
command.  What does the input windowing do for the command?

> THREAD is also complicated to do output windowing on because of the nature 
> of the hierarchical data it outputs.

Yes. But a bit of graph colouring doesn't sound scary, compared to the
Zawinski algorithm THREAD describes.

--Arnt

v2.23.0 | Report a Bug | By Email