Here's what I have:
Program A.
does an "initserverSocket" request -> HANDLE1
does an "acceptConneciton" request -> HANDLE2
does a "closeSocket(HANDLE1)"
executes "phantom Program A" (to wait for another connection).
loops through
readSocket(HANDLE2) until done (connection closes)
does a "closeSocket(HANDLE2)"
processes data received
ends
oook.
I start the system with a "phantom run Program A"
open a telnet connection, it's accepted able to enter data (computer 1)
open a telnet connection, it's accepted able to enter data (computer 2)
open a telnet connection, it's accepted able to enter data (computer 3)
now the strange part, if any of those connections closes, all connections
will immediately closes.
After a little debugging, I found that when Program A restarts for the
2nd/3rd.. time
the initserverSocket request an error 35 (already being used), I didn't have
an
error routine to trap that, so it kept on going through the program, and it
was
given a new HANDLE2 each time from the acceptConnection routine.
here's my quandry....I have to execute initserverSocket to get a HANDLE1 whch is
required for the acceptConnection routine, if I don't allow the program A to
continue after the error 35 (and somehow is using a valid HANDLE1), I won't
be able to open session 2 and session 3 until session 1 is closed.
How does one set this up, so simultaneous connections can be made to the SAME
port, and when one session closes, it doesn't close all sessions?
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
