Home/ Questions/Q 7061589
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T04:29:34+00:00

A server is listening, let’s say, on port 3000. When he receives a connection

  • 0

A server is listening, let’s say, on port 3000. When he receives a connection request and the connection is successful, if i call a function, let’s say “getRemotePort” it will say 1234. My question is, the server will send data to the remote devise (client) on port 1234, but what about the other way around? Will the client keep sending data on the same port, in this case 3000? So everything that the server will receive (connection requests and other data) will come through the same port?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team
    1. Yes it will
    2. This is not a problem.

    The point behind this is, that a connection is defined by the (LocalIP, LocalPort, RemoteIP, RemotePort) tupel – this is the only combination, that has to be unique.

    On the performance side, this is no problem as well: A port is a logic construct, that has no limiting effect on the throughput of a connection, some edge cases aside (Very high latency combined with very high throughput can create a case, where a single connection can not saturate a physical link, so a second connection, requiring a second port, can speed things up. Mind though, that even in this case not the port count, but the connection count is to blame – they just happen to be 1:1)

    • 0