From 1d236e649df10515bf042fa2283eef509648d9c9 Mon Sep 17 00:00:00 2001 From: Eric Wong Date: Wed, 30 Sep 2015 21:00:25 +0000 Subject: nntp: implement OVER/XOVER summary in search document The document data of a search message already contains a good chunk of the information needed to respond to OVER/XOVER commands quickly. Expand on that and use the document data to implement OVER/XOVER quickly. This adds a dependency on Xapian being available for nntpd usage, but is probably alright since nntpd is esoteric enough that anybody willing to run nntpd will also want search functionality offered by Xapian. This also speeds up XHDR/HDR with the To: and Cc: headers and :bytes/:lines article metadata used by some clients for header displays and marking messages as read/unread. --- public-inbox-nntpd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'public-inbox-nntpd') diff --git a/public-inbox-nntpd b/public-inbox-nntpd index 82d68383..0035637d 100644 --- a/public-inbox-nntpd +++ b/public-inbox-nntpd @@ -52,8 +52,8 @@ sub refresh_groups () { $ng = $old_ng; } - # Only valid if Msgmap works - if ($ng->mm(1)) { + # Only valid if msgmap and search works + if ($ng->usable) { $new->{$g} = $ng; push @list, $ng; } -- cgit v1.2.3-24-ge0c7