Fri, 24 Aug 2001 15:17:46 -0400 (EDT)
> Practically, I would expect that to perform well for only those
> application protocols that were designed under roughly the same
> constraints as HTTP. i.e. text based, request/response, stateless,
> connection oriented. But this encompasses a wide array of protocols.
> I believe all of FTP, SMTP, NNTP, IMAP, POP would be included, whereas
> protocols like DNS and NFS wouldn't. That's just off the top of my
> head though.
But SMTP means I can send a message to be queued and processed
remotely, with no response from the server, and no time-out. How would
that be replicated in http?