Re: Fetching short text snippet for mails

On 2 December 2014 at 17:04, Cyrus Daboo <[email protected]> wrote:

> Hi Alexey,
>
> --On December 2, 2014 at 4:55:54 PM +0000 Alexey Melnikov <
> [email protected]> wrote:
>
>  Efficient as in eliminating the current extra round trip of doing a
>>> FETCH BODY.PEEK[<section>]<<partial>>? If so, then I think "SNIPPET"
>>> should be an alias for BODY.PEEK[the first significant text
>>> section]<<partial>>. i.e., the server does not do anything more than
>>> determine the "the first significant text section". The client still
>>> gets to use <<partial>> as it could today.
>>>
>> I thought so too. That is why I've asked the question what exactly is
>> "snippet". Unless "snippet" needs to convert from text/html to text/plain
>> (or vice versa), etc.
>>
>
> Of course there is a lot that a client might do itself to "extract" the
> snippet: convert HTML to plain text (i.e., get rid of all the <..> tags,
> scripts etc, add suitable line breaks for <h> tags), strip quoted text from
> a reply or "quote headers" from a forward.
>
> The thing is each client probably has its own heuristics as to how to
> "extract" a snippet and I am not sure we could agree on a single
> server-side approach that would do.


Yes, I entirely agree. Which is why I suspect that  trying to define a
"single server-side approach" isn't what would add the most value - you
want to define a simple protocol that returns some magic text that acts as
a snippet or preview.

Dave.

_______________________________________________
imapext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/imapext