Article View: comp.protocols.iso.dev-environ
Article #279Need some help with NIST ISODE.
From: Trei
Date: Sun, 30 Sep 1990 00:22
Date: Sun, 30 Sep 1990 00:22
18 lines
1222 bytes
1222 bytes
Help!
We seem to have come up against a serious shortcoming in the ISODE 6.0
tsaplisten facility. This is what is happening:
We have two or more processes that want to listen at the same transport
address (at mutually exclusive times). But, the first process performs its
TNetListen and TNetAccept just fine, but then when it does a TNetClose to
stop listening on the transport address, it turns out that the address is
still bound, and can't be listened on by another process until the first
process exits. This is somewhat of a dilemma for us.
If anyone knows how to work around this problem, please mail to
wheeler@mbunix.mitre.org. BTW, we are running ISODE-6.0 on a Sun 3 with
SunLink 6.0 (using TP4, not X.25).
Thanks in advance.
Technical Details
Message-ID:
<121729@linus.mitre.org>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!agate!linus!linus!mbunix.mitre.orgShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!agate!linus!linus!mbunix.mitre.org From: ptrei@mbunix.mitre.org (Trei) Newsgroups: comp.protocols.iso.dev-environ Subject: Need some help with NIST ISODE. Message-ID: <121729@linus.mitre.org> Date: 30 Sep 90 00:22:43 GMT Sender: usenet@linus.mitre.org Organization: The MITRE Corp., Bedford, MA Lines: 18