On 11/07/2010 05:55 PM, Liam wrote:
On Sun, Nov 7, 2010 at 5:58 AM, Jeroen Geilman <[email protected]
<mailto:[email protected]>> wrote:
Jeroen, thanks for your comments.
Websocket is a new protocol to enable persistent, full-duplex,
efficient connections to web servers.
However, it is just HTTP, right ?
Websockets are HTTP-initiated, but messages passed after initiation
have very low overhead, and there's no request/response sequence.
The big reason not to use IMAP is that it's not efficient for 5K+
concurrently connected clients.
Says who ? Have you tested this ?
I found a discussion about it on the dovecot mailing list.
One anecdote is hardly decisive...
I'm hoping LMTP doesn't mandate a distinct TCP connection to a
server for each message,
It supports streaming and pipelining just as SMTP does. but each
recipient is immediately accepted or permanently rejected.
Ah, so LMTP can't tell its client to try again later? It seems I'll be
writing an SMTP server...
SMTP is by design a robust, asynchronous message transport protocol.
Servers are expected to queue undeliverable mail for later delivery.
An SMTP server is expected to be able to handle anything that is thrown
at it, and queue whatever it cannot process immediately, locally, while
accepting the mail from the client.
LMTP is ALSO expected to accept all mail thrown at it, but has no
mechanism to tell the client to back off.
LMTP is unsuited to any situation where reliable delivery or queueing is
absent - even if only in a small percentage of cases.
DO make use of SMTP retrying, as it comes free - postfix already takes
care of deferred mail for you.
--
J.
