Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!elroy.jpl.nasa.gov!lll-winken!ncis.tis.llnl.gov!dog.ee.lbl.gov!ucbvax!OCFMAIL.OCF.LLNL.GOV!sumpter
From: sumpter@OCFMAIL.OCF.LLNL.GOV (Robyne Sumpter)
Newsgroups: comp.protocols.iso.dev-environ
Subject: (none)
Message-ID: <9103280050.AA26872@ocfmail.ocf.llnl.gov>
Date: 28 Mar 91 00:50:42 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 29

Hi,

	I am using the TNetListen and TNetAccept routines in isode 6.0 to
accept new connections in a server.  I have noticed that when using the 
constant NOTOK as the timeout parameter to TNetAccept, the connection is
established and the argument vector is filled in when the TNetAccept call
returns.  
	When I use any other value in the timeout parameter, such as a 
60 second timeout value or the constant OK to indicate polling, I have to
call TNetAccept twice after the connection request arrives to get the 
argument vector filled in.
	Can anyone give me some information regarding why I have to call 
TNetAccept twice?  Is it possible to only call it once and have the connection
completely established without using the NOTOK constant for a timeout?
	This is causing problems when 2 connection requests arrive within a 
very short time from eachother.  It seems as though the second call to
TNetAccept is accepting the second connection request and then returning the
file descriptor for the first connection.  
	I am trying use ISODE over a multitasking package using 
non-blocking i/o and I would like a different task to accept the second 
connection request.

	Any info would be appreciated.  Responses can be emailed.  Thanks
in advance.


Robyne Sumpter
Lawrence Livermore Lab
sumpter@ocfmail.ocf.llnl.gov