From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: downloading attachments on demand
Date: 19 Apr 2006 14:40:07 -0400 [thread overview]
Message-ID: <4nwtdl2yuw.fsf@asimov.bwh.harvard.edu> (raw)
In-Reply-To: <87hd4qziqv.fsf@latte.josefsson.org> (Simon Josefsson's message of "Tue, 18 Apr 2006 23:17:12 +0200")
On 18 Apr 2006, jas@extundo.com wrote:
> "Ted Zlatanov" <tzz@lifelogs.com> writes:
>
>> On 18 Apr 2006, jas@extundo.com wrote:
>>
>>> Alternatively, as I believe I have proposed before, we could add a
>>> new backend interface to allow Gnus to query the MIME structure of
>>> articles, and then only request partial articles, and handle the
>>> Gnus cache coherency stuff in Gnus instead of in some
>>> nnimap-specific command.
>>
>> Can we combine this work with the flags work we discussed a while ago
>> (arbitrary flags/tags)?
>
> I don't see much connection, actually. How would you combine these
> two things?
I don't mean they are directly connected, but that they both require a
rethinking of the backend API. If they both require it, it's better
to do a major change like that just once.
>> It would probably be easier to do a major backend addition like that
>> in one effort instead of twice.
>
> Adding a backend interface isn't that difficult.
I mean the backend API. It should change to allow body structure
queries and arbitrary tags. I don't think in its current form it can
do either easily, but perhaps I'm wrong.
>> It may also be worthwhile to look at the entire nn* backend system and
>> how it's implemented in each backend. I'm sure there are lessons to
>> be learned and code that could be rewritten for better performance or
>> reliability.
>
> Yup.
This, too, could require significant changes... So I would suggest
combining all that work in one project instead of spreading the pain
and knowledge over several projects.
Ted
prev parent reply other threads:[~2006-04-19 18:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 20:53 Sam Steingold
2006-04-11 6:13 ` Lars Magne Ingebrigtsen
2006-04-11 15:36 ` Sam Steingold
2006-04-11 20:26 ` Jouni K Seppanen
2006-04-12 4:38 ` Lars Magne Ingebrigtsen
2006-04-17 15:18 ` Sam Steingold
2006-04-17 15:30 ` Lars Magne Ingebrigtsen
2006-04-18 9:18 ` Simon Josefsson
2006-04-18 16:25 ` Lars Magne Ingebrigtsen
2006-04-18 21:12 ` Simon Josefsson
2006-04-18 20:24 ` Ted Zlatanov
2006-04-18 21:17 ` Simon Josefsson
2006-04-19 18:40 ` Ted Zlatanov [this message]
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=4nwtdl2yuw.fsf@asimov.bwh.harvard.edu \
--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).