diff options
author | Eric Wong <e@80x24.org> | 2015-09-30 21:00:25 +0000 |
---|---|---|
committer | Eric Wong <e@80x24.org> | 2015-09-30 21:09:23 +0000 |
commit | 1d236e649df10515bf042fa2283eef509648d9c9 (patch) | |
tree | 504b59e2c719f948b3f3224935ae212941d79a7c /t/nntpd.t | |
parent | 3393117e5ff8faef209bbf4988a59743f00b2a80 (diff) | |
download | public-inbox-1d236e649df10515bf042fa2283eef509648d9c9.tar.gz |
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.
Diffstat (limited to 't/nntpd.t')
-rw-r--r-- | t/nntpd.t | 25 |
1 files changed, 24 insertions, 1 deletions
@@ -151,7 +151,30 @@ EOF '<nntp@example.com>', '', '202', - '1' ] }, "XOVER works"); + '1' ] }, "XOVER range works"); + + is_deeply($n->xover('1'), { + '1' => ['hihi', + 'Me <me@example.com>', + 'Thu, 01 Jan 1970 06:06:06 +0000', + '<nntp@example.com>', + '', + '202', + '1' ] }, "XOVER by article works"); + + { + syswrite($s, "OVER $mid\r\n"); + $buf = ''; + do { + sysread($s, $buf, 4096, length($buf)); + } until ($buf =~ /^[^2]../ || $buf =~ /\r\n\.\r\n\z/); + my @r = split("\r\n", $buf); + like($r[0], qr/^224 /, 'got 224 response for OVER'); + is($r[1], "0\thihi\tMe <me\@example.com>\t" . + "Thu, 01 Jan 1970 06:06:06 +0000\t" . + "$mid\t\t202\t1", 'OVER by Message-ID works'); + is($r[2], '.', 'correctly terminated response'); + } ok(kill('TERM', $pid), 'killed nntpd'); $pid = undef; |