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

[Arnt Gulbrandsen <[e-mail]>]

On 08/05/2010 02:14 PM, Alexey Melnikov wrote:
> I am not sure I am getting this. Presenting found messages in UI is not
> the only way to use SEARCH.

True.

> Let's imagine that a client wants to download all messages in a thread
> for offline use. Surely the set of messages considered "in the thread"
> will be different depending on threading mechanism used.

OK, consider that. I do something like that (that's I-as-user preseeding 
a cache) using INTHREAD OR YOUNGER 604800 UNSEEN. To my mind, that's 
just one of many good-enough approximations. The ideal is "what arnt 
will want", and the smallest algoritmically specified superset of that 
is ALL, which would occasionally be painful via UMTS.

Anyway, in my opinion any good approximation of "what arnt will want" is 
good enough. I could change YOUNGER 604800 to a different nubmer of 
days, or change UNSEEN to RECENT, or use a different threading 
algorithm, and the result should also be good enough. Not significantly 
different.

But this use case doesn't need lots of approximations, any one good 
approximation will do. Therefore this use case does not justify 
THREAD=x. IMO.

Arnt