Hi Dennis,
SocketSpy works that way. If a client opens 6 sessions then SocketSpy
will open 6 sessions to the other server using 6 TWSocket created on the
fly.
Met vriendelijke groeten,
Wilfried Mestdagh
Op 17-04-16 om 15:57 schreef IT+NET - Dennis Siggaard:
Hi Wilfried,
I have already looked at the SocketSpy example once, but this time I got it to
work, Thanks :)
But I got one last problem, that I am not sure can be solved at all ?
The PC2 webserver is listening (OK)
The PC2 TWSocketLocal can connect to the PC2 Webserver (ok)
The PC2 TWSocketExt can connect to PC1 TWSocketServerExt (ok)
The PC2 TCP bridge is working both ways (ok) (I see the right traffic flowing
both ways)
The PC1 TWSocketServerExt is listening (OK)
The PC1 TWSocketServerLocal is listening (OK)
The PC1 TCP bridge is working both ways (ok) (I see the right traffic flowing
both ways)
When I telnet to PC1:80 then everything seems to be okey traffic is flowing
perferctly in both TCP bridges, but... surprise.
When I use a webbrowser to connect to PC1:80, it creates multiply connections
to PC1:80. (6 connections at the same time)
>From my point of view, it would be impossible to bridge these (extra)
connections, because there will always only be ONE connection (PC2 TWSocketExt
connect to PC1 TWSocketServerExt)
Is this an dead end, or can you see something that I can't ?
I really spend many hours to get to this point. :(
Dennis.
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
