Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <wjhardaker@ucdavis.edu>
Cc: (ding) GNUS Mailing List <ding@ifi.uio.no>
Subject: Re: gnus-group-get-new-nnml
Date: 21 Jan 1998 14:02:05 -0800	[thread overview]
Message-ID: <x7oh15mqoy.fsf@des.castles.com> (raw)
In-Reply-To: Colin Rafferty's message of "21 Jan 1998 15:40:11 -0500"

>>>>> On 21 Jan 1998 15:40:11 -0500, Colin Rafferty <craffert@ml.com> said:

Colin> I have 88 mail groups (all at level 2 (nntp is level 3)).
Colin> Doing a '2 g' is equivalent to doing M-g on each group, each of
Colin> which does an nnml-request-scan.

Colin> That's slow on an NFS mounted spool.  I don't even want to
Colin> imagine the costs of POP.

Doesn't matter...  nnml-request-scan scan's the first one, downloads
*all* of the pop's stuff and stores the incoming file, splits it and
delivers it all on the first call to it.  After that, it probably
polls the pop demon but its always empty, so its fairly fast...  Not a 
problem.  I don't have 88 groups, only about 20 or so, but I don't
have a lag time problem, after the inital download...

Colin> I needed something that would do a single nnml-request-scan,
Colin> and then update the appropriate groups lines.

That would be better I suppose (actually, its what I thought it was
doing!  I hadn't noticed it was doing multiple calls to the pop demon, 
but your right, it probably is)

-- 
"Ninjas aren't dangerous.  They're more afraid of you than you are of them."


      reply	other threads:[~1998-01-21 22:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87vhvdyh50.fsf@phaedrus.uchicago.edu>
1998-01-21 16:47 ` gnus-group-get-new-nnml Colin Rafferty
1998-01-21 17:11   ` gnus-group-get-new-nnml Wes Hardaker
1998-01-21 20:40     ` gnus-group-get-new-nnml Colin Rafferty
1998-01-21 22:02       ` Wes Hardaker [this message]

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=x7oh15mqoy.fsf@des.castles.com \
    --to=wjhardaker@ucdavis.edu \
    --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).