Gnus development mailing list
 help / color / mirror / Atom feed
From: Daniel Pittman <daniel@rimspace.net>
To: ding@gnus.org
Subject: Re: Gnus' speed
Date: Fri, 31 Jul 2009 15:06:09 +1000	[thread overview]
Message-ID: <87k51pmofy.fsf@rimspace.net> (raw)
In-Reply-To: <87d47i70sy.fsf@lifelogs.com>

Ted Zlatanov <tzz@lifelogs.com> writes:
> On Thu, 30 Jul 2009 15:58:37 +1000 Daniel Pittman <daniel@rimspace.net> wrote: 
>
> DP> Ted Zlatanov <tzz@lifelogs.com> writes:
>>> I think the backend rewrite would be fairly minor, but there are many
>>> internal and user-visible functions in Gnus that also will need to be
>>> modified.  It's a lot of work.
>
> DP> I think that saying "fairly minor" is misleading here: adding the capability
> DP> to the IMAP backend isn't enormously hard, but defining a sound (and portable)
> DP> API, and implementing it, is quite non-trivial.
>
> I'd do it with the IMAP convention of "1.2.3" to mean part 3 of part 2 of
> part 1 as an optional parameter for the backend command to fetch the body,
> and an extra backend command to get a message's structure (list of strings
> as above with the associated data).

Given that the IMAP data structure is more or less an sexpr, using that fairly
directly made sense to me.  Given it is really the only model, too, with any
widespread use ...

[...]

> Your itemized list seems very thorough and you've obviously thought
> about this more than I.  Are you interested in coordinating this effort?

At the moment, no, otherwise I would probably be writing the code instead of
just talking about it.  As it is, I looked at this a couple of years back, so
my knowledge might well be out-of-date.

Sorry.  I hate to just offer advice and not actual code, but I don't think
volunteering for the later will help anyone out.

Regards,
        Daniel
-- 
✣ Daniel Pittman            ✉ daniel@rimspace.net            ☎ +61 401 155 707
               ♽ made with 100 percent post-consumer electrons




  reply	other threads:[~2009-07-31  5:06 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-28 18:34 Daniel Clemente
2009-07-28 21:03 ` Leo
2009-07-29  8:03   ` Daniel Clemente
2009-07-29  8:44     ` David Engster
2009-07-29 11:03       ` Karl Kleinpaste
2009-07-29 11:59         ` David Engster
2009-07-29 12:26           ` Karl Kleinpaste
2009-07-29 12:44             ` David Engster
2009-07-29 18:30               ` Ted Zlatanov
2009-07-29 20:19                 ` Tom Tromey
2009-07-30  6:03                   ` Daniel Pittman
2009-07-31  6:30                 ` Bill White
2009-07-29 18:46           ` Reiner Steib
2009-08-15  1:07           ` Miles Bader
2009-08-15  1:50             ` Daniel Pittman
2009-07-29 18:25       ` Ted Zlatanov
2009-07-29  9:47     ` Leo
2009-07-29 18:24     ` Ted Zlatanov
2009-07-30  5:58       ` Daniel Pittman
2009-07-30 13:33         ` Ted Zlatanov
2009-07-31  5:06           ` Daniel Pittman [this message]
2009-08-02 14:20       ` Steinar Bang
2009-08-03 14:38         ` Ted Zlatanov
2009-07-30  5:59     ` Daniel Pittman
2009-07-29  7:07 ` CHENG Gao
2009-07-29 18:20   ` nnrss through Google Reader (was: Gnus' speed) Ted Zlatanov
2009-07-31 13:44     ` nnrss through Google Reader Ted Zlatanov
2009-07-30  0:38   ` Gnus' speed Kevin Ryde
2009-07-29 18:55 ` Reiner Steib
2009-07-30  0:29   ` Kevin Ryde
2009-07-30  7:41     ` Adam Sjøgren
2009-08-04  1:10       ` Kevin Ryde
2009-08-15  1:11     ` Miles Bader
2009-08-15  8:28       ` Steinar Bang
2009-08-16  3:50         ` Miles Bader
2009-08-04 17:48   ` Daniel Clemente
2009-08-04 17:46 ` Daniel Clemente
2009-08-05  5:52   ` Steinar Bang
2009-08-05  5:55     ` Steinar Bang
2009-08-05  8:20       ` Daniel Clemente
2009-08-05 15:10         ` Steinar Bang

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=87k51pmofy.fsf@rimspace.net \
    --to=daniel@rimspace.net \
    --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).