Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: nnml/nnfolder marks faster
Date: Tue, 25 Sep 2001 13:08:30 -0400	[thread overview]
Message-ID: <m34rpr2o63.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <ilu1ykvi556.fsf@barbar.josefsson.org> (Simon Josefsson's message of "Tue, 25 Sep 2001 18:53:09 +0200")

Simon Josefsson <jas@extundo.com> wrote:
> Seen: Each Gnus instance keeps track of which articles you have seen
> and displays a `.' secondary mark on "unseen" articles.
>
> Recent: The back end keeps track of which articles you haven't seen,
> and Gnus displays a `N' secondary mark of "recent" articles.

So changes to Seen marks are initiated by Gnus, and changes to Recent
marks are initiated by servers (not backends, I think - nnimap just
relays the Recent marks it gets from the server, it doesn't track them
internally, right?).

I think backends just pass marks between servers and Gnus.  They don't
know where changes are initiated; they just keep everybody
synchronized.  If backends store Seen, nothing changes - it just makes
it easier for users to manipulate those marks from outside Gnus.  They
wouldn't normally do this, but if they want to, why try to stop them?


paul


  reply	other threads:[~2001-09-25 17:08 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-08 19:38 Simon Josefsson
2001-09-12 19:42 ` Dan Christensen
2001-09-14 13:43   ` Simon Josefsson
2001-09-14 14:51     ` Paul Jarc
2001-09-14 17:32       ` Simon Josefsson
2001-09-14 18:08         ` Paul Jarc
2001-12-30  3:52           ` Lars Magne Ingebrigtsen
2001-12-31 10:02             ` Paul Jarc
2001-12-31 10:07               ` Lars Magne Ingebrigtsen
2001-12-31 10:28                 ` Paul Jarc
2001-12-31 10:34                   ` Lars Magne Ingebrigtsen
2001-12-31 10:56                     ` Paul Jarc
2001-12-31 10:59                       ` Lars Magne Ingebrigtsen
2001-12-31 11:20                         ` Paul Jarc
2001-09-14 18:11     ` Dan Christensen
2001-09-14 18:23       ` Dan Christensen
2001-09-20 18:38         ` Simon Josefsson
2001-09-21 15:00           ` Dan Christensen
2001-09-21 16:23             ` Simon Josefsson
2001-09-22 15:29               ` Dan Christensen
2001-09-22 16:53                 ` Simon Josefsson
2001-09-22 21:19                   ` Paul Jarc
2001-09-22 22:50                     ` Simon Josefsson
2001-09-23  6:17                       ` Paul Jarc
2001-09-23 10:13                         ` Simon Josefsson
2001-09-23 15:13                           ` Harry Putnam
2001-09-23 16:56                             ` Nevin Kapur
2001-09-23 20:46                               ` Simon Josefsson
2001-09-23 20:39                             ` Simon Josefsson
2001-09-23 22:50                             ` Kai Großjohann
2001-09-25  3:25                           ` Paul Jarc
2001-09-25 10:04                             ` Simon Josefsson
2001-09-25 15:45                               ` Paul Jarc
2001-09-25 16:53                                 ` Simon Josefsson
2001-09-25 17:08                                   ` Paul Jarc [this message]
2001-09-24 17:03                   ` Dan Christensen
2001-09-24 17:40                     ` Simon Josefsson
2001-09-25  2:28                       ` Dan Christensen
2001-09-25 17:19                         ` Simon Josefsson

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=m34rpr2o63.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    /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).