From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: "Ding Mailing List" <ding@gnus.org>
Subject: Re: fetch only a portion of an article? (nnimap mainly)
Date: 7 Mar 2005 13:11:16 -0500 [thread overview]
Message-ID: <4nbr9vfhrv.fsf@lifelogs.com> (raw)
In-Reply-To: <iluu0nrja91.fsf@latte.josefsson.org> (Simon Josefsson's message of "Fri, 04 Mar 2005 23:51:06 +0100")
On Fri, 04 Mar 2005, jas@extundo.com wrote:
> IMAP support partial retrieval (byte counts), and even retrieval based
> on the selected MIME structures (i.e., retrieve entire message except
> one big attachment). I think the problem may be in designing the back
> end interface properly, so it is flexible enough.
Can you write the nnimap function to get N bytes with an extra
parameter (you can merge it with nnimap-request-article-part or not,
up to you)?
I'll do the rest of the API.
> Ideally there should be some way to retrieve the MIME structure of
> an article, and then make Gnus chose which MIME parts to retrieve.
I'll take a look at that stuff. Unfortunately the other backends
don't support this, so it's less useful than a line count IMO
(although it can make the Gnus IMAP experience much better).
> But having a line count may be sufficient as a start. However,
> there is a big problem with caching. If an incomplete article ends
> up in the asynchronous pre-fetcher, agent cache, user cache, etc, it
> will require some tinkering to invalidate that copy and force a
> re-query on the entire article.
I can deal with this, I think. I looked at the code and it's not too
bad. I just won't enter the article in the cache if it was fetched
partially. Do you think this is OK? When and if retrieval by MIME
part is done I can change this, but for now it seems like a good
compromise.
Ted
next prev parent reply other threads:[~2005-03-07 18:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 19:52 Ted Zlatanov
2005-03-04 22:51 ` Simon Josefsson
2005-03-07 18:11 ` Ted Zlatanov [this message]
2005-03-07 19:26 ` Simon Josefsson
2005-03-08 15:58 ` Ted Zlatanov
2005-03-08 17:54 ` Simon Josefsson
2005-03-22 19:30 ` Ted Zlatanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4nbr9vfhrv.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).