Re: nnimap-split-download-body feature request

[Simon Josefsson <jas@extundo.com>]

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Thu, 20 Nov 2003, jas@extundo.com wrote:
>
>> Ted Zlatanov <tzz@lifelogs.com> writes:
>
>>> Nah, just fetch the headers.  I think that's all you can reasonably
>>> expect as a Gnus user.  Maybe fake the body with "BODY TOO LARGE"
>>> or something like that, or add a header, but I personally think
>>> that retrieving just the headers in such a case is a perfectly good
>>> solution.
>> 
>> The asynchronous prefetch, agent, cache (and possibly more things)
>> would cache this incomplete article.  How would they know the
>> message was incomplete?  After requesting a re-fetch of the entire
>> article, all those cached copies will need to be purged.  Sounds
>> like work.
>
> I'm not sure I understand.  Here's a patch to show you what I think
> could be done, since nnimap-split-articles already decides between
> the head and the whole body.  The nnimap-check-body-size function
> needs to be provided, but I hope you see what I mean.

Ah!  Sorry, I forgot we were still talking about nnimap split.  Yes,
it sounds like a good idea.  nnimap-check-body-size would probably
look like (< (imap-fetch ARTICLE "RFC822.SIZE" 'RFC822.SIZE)
nnimap-split-download-body-size) or something.