Gnus development mailing list
 help / color / mirror / Atom feed
From: Russ Allbery <rra@stanford.edu>
To: ding@gnus.org
Subject: Re: Gnus always fetching all messages from nntp server
Date: Sun, 21 Nov 2010 22:41:20 -0800	[thread overview]
Message-ID: <878w0lami7.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <m3hbfak0hs.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 21 Nov 2010 19:14:23 +0100")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> There's no way to do that without fetching all the headers for all the
> articles in the group.  NNTP doesn't offer a "return headers for the
> threads where these articles appear in".

Well, you can get all parents by retrieving overview information by
message ID (OVER <msgid>), and if the server supports XPAT on References,
you can get the rest of the thread with XPAT searches.  I'm not sure if it
would end up being more efficient than what Gnus is doing now, due to the
round trips required, but it would send less data over the network.

-- 
Russ Allbery (rra@stanford.edu)             <http://www.eyrie.org/~eagle/>



  parent reply	other threads:[~2010-11-22  6:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-20  9:01 Gabe Logan
2010-11-21  4:26 ` Lars Magne Ingebrigtsen
2010-11-21  7:32   ` Gabe Logan
2010-11-21  7:37     ` Lars Magne Ingebrigtsen
2010-11-21 10:30       ` Gabe Logan
2010-11-21 18:14         ` Lars Magne Ingebrigtsen
2010-11-22  6:15           ` Gabe Logan
2010-11-22  6:41           ` Russ Allbery [this message]
2010-11-24 21:15             ` Lars Magne Ingebrigtsen
2010-11-24 21:22               ` Russ Allbery
2010-11-25 10:44               ` Steinar Bang
2010-11-25 14:27                 ` 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=878w0lami7.fsf@windlord.stanford.edu \
    --to=rra@stanford.edu \
    --cc=ding@gnus.org \
    /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).