From: Sergey Matveev Date: Tue, 17 Jan 2017 19:02:36 +0000 (+0300) Subject: POP3/IMAP4 replacement use case X-Git-Tag: 0.3^2~2 X-Git-Url: http://www.git.cypherpunks.su/?a=commitdiff_plain;h=ee50d25ab1899b55edf8bf9d65f734f17cc86e97;p=nncp.git POP3/IMAP4 replacement use case --- diff --git a/doc/usecases.texi b/doc/usecases.texi index 8067a93..d45eeb4 100644 --- a/doc/usecases.texi +++ b/doc/usecases.texi @@ -3,6 +3,7 @@ @menu * Occasional connection to mail server: UsecaseMail. +* Lightweight fast POP3/IMAP4 replacement: UsecasePOP. * Unreliable/expensive communication link: UsecaseUnreliable. * Slow/expensive link for high-volume data, bad QoS: UsecaseQoS. * Extreme terrestrial environments, no link: UsecaseNoLink. @@ -38,6 +39,22 @@ stored in NNCP @ref{Spool, spool}, that after exchanging and tossing will call local @command{sendmail} command to deliver them just like that happened on the same machine. +@node UsecasePOP +@section Lightweight fast POP3/IMAP4 replacement + +@ref{nncp-daemon} can be connected with @ref{nncp-caller} for a long +time -- it can create TCP connection that lasts for many hours. When +SMTP server receives mail, it will call @ref{nncp-mail} creating an +outbound encrypted packet. Daemon checks outbound directory each second +and immediately sends notification about undelivered packets to remote +side, that also downloads it at once. + +There are only dozens of bytes notifying about incoming packets, dozens +of bytes telling to download those packets. Mail packets are compressed +(POP3 and IMAP4 as a rule do not). You have lightweight, compressed, +low-delay, reliable link for the mail with strong encryption and mutual +sides authentication! + @node UsecaseUnreliable @section Unreliable/expensive communication link