Gnus development mailing list
 help / color / mirror / Atom feed
From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: Why article numbers?
Date: Sun, 23 Feb 2003 18:23:24 +0100	[thread overview]
Message-ID: <843cme52sz.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <ilufzqf6imk.fsf@latte.josefsson.org>

Simon Josefsson <jas@extundo.com> writes:

> kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
>
>> Yeah.  What I think should happen is a renumbering.  For the cache,
>> renumbering is actually easier, most of the time: just renumber the
>> cached articles to start at 1, and you'll be fine in most cases.
>
> What if there is an article with number 1 on the server?  (But see
> below too.)

That's why I said `in most cases'.  Hm.

Gnus could offset all numbers by the number of cached articles in the
group -- then the backend would have to know about it and it would
have to treat all incoming article numbers appropriately.  Whee...

>> The copies in the agent are a thornier issue.  I think it would not
>> be good to just delete them: they will then be fetched again from the
>> server, which is a waste of bandwidth that we wanted to avoid by
>> using the agent in the first place...
>
> Yes, although that is an optimization.  Deleting them would at least
> make things correct.

Yes.  Hm.  Yeah, why not make it correct and slow first.

One possible optimization would be to find out if the uidvalidity
change actually resulted in different article numbers being used.  I
have the impression that this is often not the case.

>> Maybe the cache should be treated a little bit like a separate
>> backend, kind of like nnvirtual does it, at least conceptually.  I
>> think it would be best to just decouple the numbers used in the cache
>> totally from the numbers used on the server.  This leads to problems
>> when the cached articles are still on the server, but oh, well.
>
> This sounds like a good idea.  So conceptually there is a nncache
> which contains the articles you put into it with `*', and the nncache
> groups mirror all your normal groups.  And when you enter a group it
> is like entering a nnvirtual that contains the nncache group and the
> real group.

That was my idea.

> OTOH it sounds like work, and might expose other unwanted behaviour,
> so I'm not sure if it is worth the time to really implement it like
> this...

Hah, if it wasn't work it'd be implemented already ;-)

-- 
A preposition is not a good thing to end a sentence with.



  reply	other threads:[~2003-02-23 17:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-07 21:55 Kai Großjohann
2003-02-08 20:38 ` Lars Magne Ingebrigtsen
2003-02-08 23:44   ` Paul Jarc
2003-02-08 23:49     ` Lars Magne Ingebrigtsen
2003-02-09 14:59       ` Kai Großjohann
2003-02-10 18:40       ` Paul Jarc
2003-02-22 20:24         ` Lars Magne Ingebrigtsen
2003-02-22 21:11           ` Kai Großjohann
2003-02-22 21:24             ` Lars Magne Ingebrigtsen
2003-02-22 21:37               ` Kai Großjohann
2003-02-22 21:44                 ` Lars Magne Ingebrigtsen
2003-02-23  9:51                   ` Kai Großjohann
2003-02-22 22:33             ` Simon Josefsson
2003-02-23  9:52               ` Kai Großjohann
2003-02-23 11:04                 ` Simon Josefsson
2003-02-23 13:33                   ` Kai Großjohann
2003-02-23 16:56                     ` Simon Josefsson
2003-02-23 17:23                       ` Kai Großjohann [this message]
2003-02-23 11:34                 ` Lars Magne Ingebrigtsen
2003-02-23 16:56                 ` Michael Shields
2003-02-22 21:43           ` Paul Jarc
2003-02-23  5:03             ` Michael Shields
2003-02-23 10:28             ` Kai Großjohann
2003-02-23 11:38             ` Lars Magne Ingebrigtsen

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=843cme52sz.fsf@lucy.is.informatik.uni-duisburg.de \
    --to=kai.grossjohann@uni-duisburg.de \
    /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).