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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,297123c81a4f80e1 X-Google-Attributes: gid103376,public From: tmoran@bix.com Subject: Re: Socket buffer filling up Date: 1999/11/19 Message-ID: <5qjZ3.555$mf6.21967@typhoon-sf.snfc21.pbi.net>#1/1 X-Deja-AN: 550702921 References: <86aeoafdsq.fsf@ppp-162-48.villette.club-internet.fr> X-Complaints-To: abuse@pacbell.net X-Trace: typhoon-sf.snfc21.pbi.net 943047425 206.170.2.162 (Fri, 19 Nov 1999 13:37:05 PST) Organization: SBC Internet Services NNTP-Posting-Date: Fri, 19 Nov 1999 13:37:05 PST Newsgroups: comp.lang.ada Date: 1999-11-19T00:00:00+00:00 List-Id: >possible to check that the peer on the socket is still here without How about "getpeername"? Or if you are using a WSAAsync socket you can of course get a message when the connection is dropped. (With raw Winsock. With CLAW you would likely call procedure Get_Peer or overide the inherited procedure When_Disconnect.)