From owner-freebsd-hackers  Tue May 27 17:39:19 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id RAA12108
          for hackers-outgoing; Tue, 27 May 1997 17:39:19 -0700 (PDT)
Received: from cypher.net (black@zen.pratt.edu [205.232.115.155])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA12084
          for <FreeBSD-Hackers@FreeBSD.ORG>; Tue, 27 May 1997 17:39:13 -0700 (PDT)
Received: (from black@localhost) by cypher.net (8.8.5/8.7.1) id UAA09050; Tue, 27 May 1997 20:38:33 -0400
Date: Tue, 27 May 1997 20:38:31 -0400 (EDT)
From: Ben Black <black@zen.cypher.net>
To: Terry Lambert <terry@lambert.org>
cc: cmsedore@mailbox.syr.edu, rssh@cki.ipri.kiev.ua,
        FreeBSD-Hackers@FreeBSD.ORG
Subject: Re: async socket stuff
In-Reply-To: <199705280034.RAA00781@phaeton.artisoft.com>
Message-ID: <Pine.LNX.3.91.970527203636.1463P-100000@zen.cypher.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> It's not generally useful, either.  For instance, for POP3 and SMTP
> mail processing, "." quoting must take place.  You have to adulterate
> the RFC's and *store* the data quoted (assuming that it will be going
> out on the same type of, or similar, transport it came in on) if you
> wish to use this facility for, for instance, POP3 lookup or SMTP
> forwarding.
> 

i guess i wasn't forceful enough in my belief that it was a far too 
specialized thing to put in the kernel.  i think i handled it in later 
posts, but thanks for the excellent example.


b3n