put rationale in the manpage

diff --git a/RATIONALE b/RATIONALE
deleted file mode 100644 (file)
index 17b73ad..0000000
--- a/RATIONALE
+++ /dev/null
@@ -1,21 +0,0 @@
-Why not innfeed ?
-
-Two reasons:
-
-1. innfeed is not reliable[1].  In particular, the program feed
-   protocol spoken between innd and innfeed is lossy: if innfeed dies
-   unexpectedly, articles which innd has written to the pipe to
-   innfeed will be skipped.  innd has no way of telling which articles
-   those are, no useful records, and no code to retry.  I can see no
-   sensible way to solve this problem without using a different
-   approach to getting articles from innd.
-
- [1] By "reliable" I mean that articles will be propagated unless
-     either (a) there is some deliberate policy or technical reason
-     why they are not or (b) transient problems prevent the
-     propagation from succeeding before the article expires.
-
-2. Why not just edit innfeed ?  Well, innfeed is an very large program
-   for what it does - nearly 25kloc.
-
-So I set out to write something similar but smaller and reliable.

diff --git a/innduct.8 b/innduct.8
index f297c2dd2e5357414641f7b33ffd82b9c1123fa9..f4a253d4ec9d66b60a576cc4e5c1d000de24b489 100644 (file)
--- a/innduct.8
+++ b/innduct.8
@@ -1,3 +1,4 @@
+'\" t
 .TH INNDUCT 8
 .SH NAME
 innduct \- quickly and reliably stream Usenet articles to remote site
@@ -432,6 +433,17 @@ separately for each peer.
 .TP
 .B innxmit
 is the actual NNTP feeder program used by nntpsend.
+.LP
+.TS
+left;
+l l l l.
+       \fBinnfeed\fR   \fBinnduct\fR   \fBnntpsend/innxmit\fR
+realtime feed  Yes     Yes     No
+reliable       No      Yes     Yes
+source code size       24kloc  4.6kloc 1.9kloc
+invoke once for all sites      Yes     No      Yes
+number of processes    one     1/site  2/site, intermittently
+.TE
 .SH EXIT STATUS
 .TP
 .B 0