Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!newsfeed.ksu.ksu.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!europa.eng.gtefsd.com!MathWorks.Com!uhog.mit.edu!grapevine.lcs.mit.edu!ginger.lcs.mit.edu!wollman From: wollman@ginger.lcs.mit.edu (Garrett Wollman) Newsgroups: comp.unix.bsd Subject: Re: "official" socket spec? Date: 4 May 1994 20:55:03 GMT Organization: MIT Laboratory for Computer Science Lines: 21 Message-ID: <2q9237$3rv@GRAPEVINE.LCS.MIT.EDU> References: <1994May3.232046.24234@unislc.slc.unisys.com> NNTP-Posting-Host: ginger.lcs.mit.edu In article <1994May3.232046.24234@unislc.slc.unisys.com>, Paul Johnson <ptj@unislc.slc.unisys.com> wrote: > I am looking for the "official" socket API spec. I think what I am >looking for is the API as defined by 4.3BSD "Tahoe". We do not have a BSD >licience. Are there any documents available to me defining the "Tahoe" >socket API? `Defining', no. However, there is a POSIX committee working on defining a standard for both the socket interface and one of the others (forget which one). You might ask the IEEE Standards Office for information on the status of this committee and its output. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman@lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. Opinions not those of| It is a bond more powerful than absence. We like people MIT, LCS, ANA, or NSA| who like Shashish. - Claude McKenzie + Florent Vollant