Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.uwa.edu.au!disco.iinet.net.au!news.uoregon.edu!vixen.cso.uiuc.edu!sdd.hp.com!hp-pcd!hpbs2500.boi.hp.com!hpax!cupnews2.cup.hp.com!raj From: raj@cup.hp.com (Rick Jones) Newsgroups: comp.unix.bsd.misc,comp.unix.sys5.r4 Subject: Re: TCP socket close() behavior (Was: Imcomplete Documents and Images from httpd) Date: 22 May 1996 17:27:42 GMT Organization: Hewlett-Packard's Network Computing Division Lines: 7 Message-ID: <4nviqe$2rf@hpindda.cup.hp.com> References: <4m7r3m$9qt@nntpb.cb.att.com> <31979d8d@yoda.omnicron.com> <MUKESH.96May22092052@lucknow.eng.sun.com> Reply-To: raj@cup.hp.com NNTP-Posting-Host: hpindio.cup.hp.com X-Newsreader: TIN [version 1.2 PL2.2] Xref: euryale.cc.adfa.oz.au comp.unix.bsd.misc:1093 comp.unix.sys5.r4:11008 I'm going to concurr with Mukesh and suggest that applications which desire more "robustness" should use the shutdown/read combination or its semantic equivalent in other APIs. It's a shame that some of the common http code libraries out there simply use close(). rick jones