From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/10954 Path: main.gmane.org!not-for-mail From: Lars Magne Ingebrigtsen Newsgroups: gmane.emacs.gnus.general Subject: Re: nnchoke-retrieve-groups and nnchoke-request-group Date: 17 May 1997 06:11:01 +0200 Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: main.gmane.org 1035150746 27463 80.91.224.250 (20 Oct 2002 21:52:26 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 21:52:26 +0000 (UTC) Return-Path: Original-Received: from ifi.uio.no (0@ifi.uio.no [129.240.64.2]) by deanna.miranova.com (8.8.5/8.8.5) with SMTP id VAA11084 for ; Fri, 16 May 1997 21:44:00 -0700 Original-Received: from claymore.vcinet.com (claymore.vcinet.com [208.205.12.23]) by ifi.uio.no with SMTP (8.6.11/ifi2.4) id for ; Sat, 17 May 1997 06:16:36 +0200 Original-Received: (qmail 20745 invoked by uid 504); 17 May 1997 04:16:34 -0000 Original-Received: (qmail 20742 invoked from network); 17 May 1997 04:16:33 -0000 Original-Received: from ifi.uio.no (0@129.240.64.2) by claymore.vcinet.com with SMTP; 17 May 1997 04:16:33 -0000 Original-Received: from proletcult.slip.ifi.uio.no (root@ppp19.larris.ifi.uio.no [129.240.68.119]) by ifi.uio.no with ESMTP (8.6.11/ifi2.4) id for ; Sat, 17 May 1997 06:16:29 +0200 Original-Received: (from larsi@localhost) by proletcult.slip.ifi.uio.no (8.8.2/8.8.2) id GAA19012; Sat, 17 May 1997 06:11:05 +0200 Mail-Copies-To: never Original-To: ding@gnus.org In-Reply-To: Greg Stark's message of 16 May 1997 18:29:02 -0400 Original-Lines: 40 X-Mailer: Gnus v5.4.52/Emacs 19.34 X-Face: &w!^oO~dS|}-P0~ge{$c!h\ writes: > In rewriting and using my backend i've realized that gnus sometimes > uses *-retrieve-groups to activate a bunch of groups and sometimes > repeatedly calls *-request-group. It will use the former if you use the `some' setting of `gnus-read-active-file' and the latter if you use the nil setting. The `some' setting will, as you've seen, never be slower than the nil setting. > On a similar note, if i set gnus-read-active-file to 'some Gnus is > smart enough to only ask for some groups, but it seems to still ask > for more than it really needs to. It seems to ask for anything that > isn't a zombie or killed group, even though i have > gnus-activate-level and gnus-activate-foreign-newsgroups set much > lower so it's asking for active file information about group > information it isn't even planning on using. That's true. Those variables aren't consulted at all when deciding what groups to ask for active info on. We need read active info on all living groups, though, to have functions like the "bogus group checking" work reliably. > I think these problems are actually related. It doesn't really make > sense to have a gnus-read-active-file variable, there should maybe > be a nntp-read-active-file which helps decide which NNTP query to > use to complete the retrieve-groups request, but there's no reason > for a user to change how the interface between Gnus and the backends > go about they're business. Well i suppose the distinction between > 'some and t is useful, but i don't think the distinction between nil > and 'some should be made by Gnus; i think that should be decided by > an nntp variable. This is decided by nntp -- if `some' is used. nil isn't a useful value, really. -- (domestic pets only, the antidote for overdose, milk.) larsi@gnus.org * Lars Magne Ingebrigtsen