From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,8f6dc5bfebaf357f
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news4.google.com!news2.google.com!proxad.net!newsfeed.stueberl.de!news.bawue.net!news.belwue.de!LF.net!news.enyo.de!not-for-mail
From: Florian Weimer <fw@deneb.enyo.de>
Newsgroups: comp.lang.ada
Subject: Re: "broken pipe" while reading/writing stream-based sockets
Date: Sat, 14 May 2005 23:27:16 +0200
Message-ID: <87zmuxqz0r.fsf@deneb.enyo.de>
References: <1115766179.505983.40960@f14g2000cwb.googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: albireo.enyo.de 1116106037 4526 212.9.189.177 (14 May 2005 21:27:17
 GMT)
X-Complaints-To: 
Cancel-Lock: sha1:uCuJc27wwW0tbKcpt4fzCl0WXy0=
Xref: g2news1.google.com comp.lang.ada:11033
Date: 2005-05-14T23:27:16+02:00
List-Id: <comp.lang.ada>

* fabio de francesco:

> 1) Why does this server sometimes crash with "Broken Pipe"?

This usually indicates that the client closed its end of the
connection while the server was still sending data.  Maybe this
happens because your code does not deal with partial reads/writes.

> 2) It seems that using Input/Output instead of Read/Write never causes
> "Broken Pipe". Why?

The stream implementation provided by GNAT.Sockets deals with partial
reads and writes.