Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: solid nnweb
Date: 28 Sep 1996 02:58:02 +0100	[thread overview]
Message-ID: <x6pw37pfit.fsf@eyesore.no> (raw)

The ephemeral nnweb groups are nice and fun, but I think solid nnweb
groups would be actually useful.

Imagine -- you create an nnweb group that matches "Mango".  nnweb
would keep an identifier<->article number mapping somewhere, so that
when you tap `M-g' on the nnweb:mango group, it would request matches
from the search engine, compare with its previously created map, and
make all the new articles, well, new.  In short, solid nnweb groups
could potentially behave like any other group.

I see two possibilities for implementing this.

1) Just keep a simple identifier-to-article number map in a file.  The
identifier would be either the (partial) URL to fetch the article or
the Message-ID.  (Depends on what data the search engine gives.)  This
would simply make read articles read and unread articles unread. 

2) Keep all the headers to all the previous search results stored in a
file.  Then commands like `C-u RET' will let you enter a summary
buffer without actually consulting the search engine.  Selecting an
article would mean fetching from the search engine site, but that's a
different matter.

Hmm...  The second alternative seems sexier.  How would old entries be
expired?  Just keep a max-size variable, and expire the oldest
entries?  I suppose that could be done...  

Ok: There would be a ~/News/nnweb/ directory with an active file, a
file to store the match regexp (and stuff) for the groups, and one
.overview file per nnweb group.  Uhm -- the active file and the regexp
file could be combined, I guess.  Yes.

So -- whaddaya think?  Ephemeral nnweb groups would work as present,
of course. 

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."


             reply	other threads:[~1996-09-28  1:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-09-28  1:58 Lars Magne Ingebrigtsen [this message]
1996-09-30  7:41 ` Wesley.Hardaker
1996-10-01  3:54   ` Lars Magne Ingebrigtsen
1996-10-03  2:19 ` Scoring colors in Red Gnus 0.47 Miguel de Icaza
1996-10-03  5:10   ` Steven L Baur
1996-10-03 17:11   ` Per Abrahamsen

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=x6pw37pfit.fsf@eyesore.no \
    --to=larsi@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).