Comment 58 for bug 322256

Revision history for this message
In , Joshua Cranmer (jcranmer) wrote :

(In reply to comment #49)
> a) Leave the rc as it is, but don't count messages that don't exist on the
> server anymore when computing the number of unreads for a group; or
> b) when it is found that a message doesn't exist anymore, mark it as read in
> the rc file so the mailer will remember that that message isn't "unread" (in
> the sense of being available for reading).

Recalling a bit from memory, the newsrc file is written by dumping the key set. I can see the value of remembering "holes" on a bigger scale, since it would be nice to know that we haven't tried looking at a block of articles. But on the other hand, if we download articles 1-1000 and don't see article 334, it's safe to assume that we won't ever see 334.

Questions to ponder on:
* What criteria should we use to determine which missing messages should be glossed over in the key set?
** (Tentative response: XOVER-time. But what about interrupted downloads?)
* How should Mark All As Read work?
** (Tentative response: reset the newsrc to <oldest>-<latest>. But how does this interact with Get Next N Messages?)
* What if we do find 334 later on?
** (Tentative response: Mark it as unread and reset read set information)

Reassigning to myself (and resetting QA). Hope bienvenu doesn't mind :-).