1
2
The tool should connect to any two TCP/IP servers and transparently route sends and receives between them. The tool should connect to both the TCP/IP servers and transparently forward any data it receives between the two.
The problem that the tool is intended to solve is that there are two networked devices, each behaving as a server. One of the devices will send TCP/IP data to its client when an event occurs on it, then other expects this data to be sent to it.
In what context? Depending on what program you are talking about, it could range any ware from "Impossible" to "Check 'client' under 'options'" – Grant – 2009-09-14T13:47:24.013
More info needed. What are you trying to accomplish? – Mark – 2009-09-14T13:56:49.203
Added some more description now. – Thomas Bratt – 2009-09-14T14:30:57.370
Usually, you need to connect two networked devices together by having one connect to the other. So the sender would open up a TCP/IP connection to the listener. Or the listener would open up a TCP/IP connection to the sender. – J. Polfer – 2009-09-14T15:57:50.137
1@sheepsimulator: this is true, but in this case I have two TCP/IP servers, both with a listening socket. Hence the problem! :) – Thomas Bratt – 2009-09-14T16:02:12.063
Can either of these two server programs be modified? – J. Polfer – 2009-09-14T16:11:52.143
@sheepsimulator: Unfortunately not. – Thomas Bratt – 2009-09-14T16:21:58.443
Are you running windows or Linux? – J. Polfer – 2009-09-14T16:22:57.710
Windows. I have updated the tags to indicate this. – Thomas Bratt – 2009-09-14T16:24:12.810
@Thomas Bratt - that sounds like an extremely sweet project. Best of luck at your trade show! – J. Polfer – 2009-09-15T13:55:38.370