Re: Port for real time HL7 transactions

Joe,

"Question - when the tunnel was created between "us" and "them", a
specific
port was designated for traffic coming to us (i.e., to our listener) and
another for return traffic (to their listener). I noticed on netstat that
the local port is correct, but the remote port varies (and is not one that
was specified). Since the socket connects, and we receive data, and I am
returning data through this same socket connection......do the remote port
need to be open for them to receive?"

I'm not sure why the tunnel was created to use two ports (one for sending
and one for receiving). Unless there are underlying reasons for doing
this, this is (to me) more complex than need be.

To my understanding a socket connection is a one to one connection that
has to be able to send and receive data and acknowledge when it does both
activities at both ends of the connection. Otherwise you can't guarantee
the integrity of the transmission.

When you connect (in listen mode) to the server, (it sounds like) all your
reads and writes are going though the port you are listening on. (That's
the way my programs work.) But with two ports (one to send and one to
receive), you would need to program your listener to detect receipt of an
ack on the other port, and coordinate the send/receive between your sender
and receiver programs.

(If I am way off base here someone please chime in and enlighten me!)


Regards, Jerry

Gerald Kern - MIS Project Leader
Lotus Notes/Domino Administrator
IBM Certified RPG IV Developer
The Toledo Clinic, Inc.
4235 Secor Road
Toledo, OH 43623-4299
Phone 419-479-5535
gkern@xxxxxxxxxxxxxxxx


This e-mail message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential and privileged
information. Any unauthorized use, disclosure or distribution is
prohibited. If you are not the intended recipient, please inform the
sender by reply e-mail and destroy this and all copies of this message.