Re: [MORG] THREAD= search return option in draft-ietf-morg-inthread-01.txt

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 09 August 2010 08:26 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: morg@core3.amsl.com
Delivered-To: morg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3813C3A6950 for <morg@core3.amsl.com>; Mon, 9 Aug 2010 01:26:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.881
X-Spam-Level:
X-Spam-Status: No, score=-101.881 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, J_CHICKENPOX_64=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iT6MbKnwvLCz for <morg@core3.amsl.com>; Mon, 9 Aug 2010 01:26:36 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 408CE3A6819 for <morg@ietf.org>; Mon, 9 Aug 2010 01:26:36 -0700 (PDT)
Received: from [10.0.0.111] (204.80-202-212.nextgentel.com [80.202.212.204]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <TF-73ABSpTnt@rufus.isode.com>; Mon, 9 Aug 2010 09:27:09 +0100
Message-ID: <4C5FBBD4.6060906@isode.com>
Date: Mon, 09 Aug 2010 09:27:00 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Dan Keen <morg@dankeen.com>
References: <4C50244C.8010401@isode.com> <4C57ECFA.3040504@gulbrandsen.priv.no> <4C58406A.7030205@isode.com> <4C5958FA.2010403@gulbrandsen.priv.no> <1281012526.6211.333.camel@kurkku.sapo.corppt.com> <4C5AB4C3.80007@gulbrandsen.priv.no> <8349DB2C-6D37-4B02-B9F6-9DA1834A3058@dankeen.com>
In-Reply-To: <8349DB2C-6D37-4B02-B9F6-9DA1834A3058@dankeen.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Timo Sirainen <tss@iki.fi>, morg@ietf.org
Subject: Re: [MORG] THREAD= search return option in draft-ietf-morg-inthread-01.txt
X-BeenThere: morg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Messaging Organization <morg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/morg>
List-Post: <mailto:morg@ietf.org>
List-Help: <mailto:morg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/morg>, <mailto:morg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Aug 2010 08:26:37 -0000

Dan Keen wrote:

>On Aug 5, 2010, at 5:55 AM, Arnt Gulbrandsen wrote:
>  
>
>>On 08/05/2010 02:48 PM, Timo Sirainen wrote:
>>    
>>
>>>So do you want it to always use THREAD=REFS or whatever the server wants
>>>to use?
>>>      
>>>
>>Either would be fine with me. I have a preference, but I'd be happy with either.
>>
>
>Devil's advocate here, but this prevents the client from being smarter.
>  
>
+1.

I don't think Arnt is making very good arguments for removing this 
feature ;-).

>Let's say we have a thread where the client knows some of the messages in the thread are malformed (don't have proper references or in-reply-to), but it doesn't have all the messages in the thread downloaded.
>
>WIthout being able to specify the threading algorithm in the search, we can't say "Hey, on this one, use Subject-based threading because we know it's malformed".
>
>Yes, the client can try to do it's own subject-based threading implementation with multiple searches to the server, but this could be an improvement.
>
>I'd agree it's not necessary, but I want to make sure we know there is a valid use case for it.
>