[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Pan-devel] Thinking out loud about tasks in 0.12.1
From: |
Charles Kerr |
Subject: |
Re: [Pan-devel] Thinking out loud about tasks in 0.12.1 |
Date: |
Thu, 6 Jun 2002 06:04:31 -0700 |
User-agent: |
Mutt/1.3.20i |
On Wed, Jun 05, 2002 at 09:24:45AM -0700, Charles Kerr wrote:
>
> Two obstacles to having tasks take message-ids instead of Article*s:
>
> (2) nntp.c is designed to take Article*'s. It uses the subject and
> linecount for status-item feedback, message-id to actually get
> the message, and calls article_set_headers for "Newsgroups:",
> "Reply-To:", "Followup-To:", and "Xref:"
>
> For the second problem, we could make the status-feedback coarser
> by moving the progressbar a little after each article is downloaded,
> rather than each line. We could have task-[save,bodies] remember the
> subject and message-id of each article it needs to download and pass
> those in to nntp.c.
>
> We don't actually use Xref: -- we get it in XOVER -- so we would probably
> be better off not looking for it in nntp_article_download_to_gstr().
>
> Likewise Newsgroups:, Reply-To:, and Followup-To: are only used when
> reading or replying to that particular article, so we should probably change
> the memory/speed tradeoff for them by not keeping them in the Article*
> tables but rather pumping them from acache when necessary.
Actually, this would be taken care of _really_ nicely if current_article
wasn't an Article, but a GMimeMessage ... :)