Gnus development mailing list
 help / color / mirror / Atom feed
From: Jan Vroonhof <vroonhof@math.ethz.ch>
Cc: ding@ifi.uio.no
Subject: Re: Changing Default News Server
Date: 18 Jul 1996 17:51:44 +0200	[thread overview]
Message-ID: <byspapr23z.fsf@math.ethz.ch> (raw)
In-Reply-To: Lars Balker Rasmussen's message of 18 Jul 1996 14:30:45 +0200

Lars Balker Rasmussen <gnort@daimi.aau.dk> writes:

> > The brute force solution would be to get the Message-ID's of all read
> > messages and then look them up on the new server.
> 
> Precisely, that's a brute force ad-hoc solution, which would absolutely
> not work if e.g. my local news-server (which has perverse expiration
> times) was involved.
> 

However it works quite well for small groups. For large groups we are
helped by the fact that the newsreading is done by a human (i.e.
slow).
If you a large group say recs.jobs.offered then most of the time
either one of these is true:

1. Only a few messages are 'read' (i.e. those you actually read).
2. Almost all are read and those that are unread are at the end
(i.e. you have used Catchup).

Case 2 is the difficult one:

Then consider say the last 100 messages of the large "read" block and
look them up on the new server. Lookup the unread articles on the new
server. Take the minum of the article numbers found This gives you a
reasonble lower bound for the unread articles.
Then proceed lower bound upwards to lookup which of the remaing
articles you have read.

This at least gives you a reasonble approximation of wat you want.

Wether this is implementable in e-lisp is another matter.

Jan

P.S. How many articles does rec.jobs.offered have on your news server?

-- 
Jan Vroonhof                    http://www.math.ethz.ch/~vroonhof/
Mathematik,                                  vroonhof@math.ethz.ch
HG E16, ETH-Zentrum,                      Tel: +41-1-6325456/25154
Raemistrasse 101, CH-8092 Zuerich.              Fax: +41-1-6321085


  reply	other threads:[~1996-07-18 15:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-07-18  4:26 Lal Samuel Varghese
1996-07-18  7:13 ` Lars Balker Rasmussen
1996-07-18 23:41   ` Steven L Baur
1996-07-18 23:43   ` David Watson
1996-07-18 23:51     ` Lars Magne Ingebrigtsen
1996-07-30 18:02       ` Ken Raeburn
1996-07-30 20:24         ` Lars Magne Ingebrigtsen
1996-07-30 22:15           ` David Lebel
1996-07-31  3:00           ` Ken Raeburn
1996-07-18 11:22 ` Darren/Torin/Who Ever...
1996-07-18 11:27   ` Lars Balker Rasmussen
1996-07-18 12:13     ` Jan Vroonhof
1996-07-18 12:30       ` Lars Balker Rasmussen
1996-07-18 15:51         ` Jan Vroonhof [this message]
1996-07-18 16:40           ` Jan Vroonhof
1996-07-19  8:56           ` Lars Balker Rasmussen

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=byspapr23z.fsf@math.ethz.ch \
    --to=vroonhof@math.ethz.ch \
    --cc=ding@ifi.uio.no \
    /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).