The phone analogy can work.
Think of it as a call center with a 1-800 number though.
There is only one inbound number (port) and the people calling have their own number but many people can all call this number at the same time as the PBX may have a T1/E1 line there handling many concurrent sessions.
Internally these sessions can be mapped to session handles and ID's so that the PBX (your server app) can send data back to the correct client.
You don't want to assign a different 1-800 number (port) for every concurrent session you want to be able to handle you just want the one number and have everyone call you there.
Better Client/Server Networking?
@Psych
You find my "Multi User Server Examples" under http://mk-soft.homepage.t-online.de/fil ... b4/server/
The old links not more avalible.
GT
You find my "Multi User Server Examples" under http://mk-soft.homepage.t-online.de/fil ... b4/server/
The old links not more avalible.
GT

My Projects ThreadToGUI / OOP-BaseClass / EventDesigner V3
PB v3.30 / v5.75 - OS Mac Mini OSX 10.xx - VM Window Pro / Linux Ubuntu
Downloads on my Webspace / OneDrive
PB v3.30 / v5.75 - OS Mac Mini OSX 10.xx - VM Window Pro / Linux Ubuntu
Downloads on my Webspace / OneDrive