Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!sdd.hp.com!spool.mu.edu!news.cs.indiana.edu!ux1.cso.uiuc.edu!resnick From: resnick@cogsci.uiuc.edu (Pete Resnick) Newsgroups: comp.sys.mac.programmer Subject: Re: MacTCP, abort an asynchronous operation, how? Message-ID: <1991Mar20.175619.23767@ux1.cso.uiuc.edu> Date: 20 Mar 91 17:56:19 GMT References: <40367@cup.portal.com> Sender: usenet@ux1.cso.uiuc.edu (News) Organization: University of Illinois at Urbana Lines: 22 ekalenda@cup.portal.com (Edward John Kalenda) writes: >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. This is just wrong. I do it, as described in my previous post, with no problems at all. I don't know what problem you encountered, or who you spoke to at Apple, but this is just incorrect. If you need a sample piece of code that does it, write and I will send it to you. pr -- Pete Resnick (...so what is a mojo, and why would one be rising?) Graduate assistant - Philosophy Department, Gregory Hall, UIUC System manager - Cognitive Science Group, Beckman Institute, UIUC Internet/ARPAnet/EDUnet : resnick@cogsci.uiuc.edu BITNET (if no other way) : FREE0285@UIUCVMD