Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!fernwood!portal!cup.portal.com!ekalenda
From: ekalenda@cup.portal.com (Edward John Kalenda)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MacTCP, abort an asynchronous operation, how?
Message-ID: <40367@cup.portal.com>
Date: Tue, 19 Mar 91 23:21:38 PST
Organization: The Portal System (TM)
References:  <KIRE.91Mar15130507@cyklop.nada.kth.se>

>I do a TCPPassiveOpen asynchronous to grab a unique tcp_port on
>my mac. That tcp_port is used when launching a server on a unix
>machine (using rexecd). The server is started as "server
>ip_addr_of_mac tcp_port_on_mac &". The first thing the server
>does is to disassociate itself from the tty (the shell will exit
>and rexecd will close its connection) and then connect to my
>"tcp_port_on_mac". I can now communicate with the server on my
>own tcp-connection.
>
>Now, if I fail to launch the server on the unix machine, no one
>will be there to connect to my tcp_port and would like to abort
>the TCPPassiveOpen operation.  

There is NO way to stop the PassiveOpen in the current release of
MacTCP unless it has had a connection first. I and my croney at
Apple has spoken to the developer of MacTCP and "It's a known bug
which will be fixed just as soon as I get to it". We solved the
problem by having our application connect to itself, thereby causing
MacTCP to be happy since a connection to the PassiveOpen happened.

Ed
ekalenda@cup.portal.com