Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Images streaming using Indy client side
#11
(05-06-2022, 10:01 AM)Ahmed Sayed Wrote: Ok, I read some about TCP/UDP hole punching and I have seen some people asking about it on stack-overflow but I don't understand how to implement it in Indy? Regardless of the protocol HTTP/TCP/UDP.

Sorry, I can't answer that.

(05-06-2022, 10:01 AM)Ahmed Sayed Wrote: I assume that these ports used in the apps are local ports and are not public and can't be reach from the public internet that's why both apps will not be able to connect to each other unless I open ports on both routers and map them to the local ports then use these public ports instead.

Correct.

(05-06-2022, 10:01 AM)Ahmed Sayed Wrote: I am not planning on making a TIdTCPClient connect to another TIdTCPClient here, in fact I want this to be easy as possible. I wanna use a normal connection between a client and a server on both sides.

Unless you can figure out how to make the hole punching work, then you will just have to configure port forwarding in one of the NAT routers, and have the other PC act as the client that connects to that router.

(05-06-2022, 10:01 AM)Ahmed Sayed Wrote: How can I get the public port?

The public port will have to be published somewhere that you can query it, or the user will have to enter it manually.

Reply


Messages In This Thread
RE: Images streaming using Indy client side - by rlebeau - 05-06-2022, 09:17 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)