From owner-freebsd-arch  Thu Jan 11  6:46:24 2001
Delivered-To: freebsd-arch@freebsd.org
Received: from critter.freebsd.dk (hades.cybercity.dk [212.242.42.118])
	by hub.freebsd.org (Postfix) with ESMTP id 6F7EF37B400
	for <freebsd-arch@FreeBSD.ORG>; Thu, 11 Jan 2001 06:46:07 -0800 (PST)
Received: from critter (localhost [127.0.0.1])
	by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f0BEjxZ08609;
	Thu, 11 Jan 2001 15:45:59 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: Dag-Erling Smorgrav <des@ofug.org>, freebsd-arch@FreeBSD.ORG
Subject: Re: Proposed chage to sbuf semantics. 
In-Reply-To: Your message of "Thu, 11 Jan 2001 07:34:40 MST."
             <200101111434.f0BEYes28373@aslan.scsiguy.com> 
Date: Thu, 11 Jan 2001 15:45:59 +0100
Message-ID: <8607.979224359@critter>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


As original perpetrator of the sbufs, I'd like to chime in briefly.

I agree with Justin about being able to succesfully retreive an
overflowed sbuf.

I would even suggest that finish replaces the final characters in
an overflowed sbuf with "[...]" as a generic marker that overflow
happened.

I also agree with Dag-Erling that the API should be entirely function 
based.

--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message