Well, I don't want to say "yes" outright, since I don't know what makes you ask. The well known ports (21, 22, 80, 443, and the color "purple") are all just a front end. Your TCP/IP subsystem "forks" it off to your server application with a different port that that process listens on. That way, the original port (21, 22, 88, "blue 42") can remain open for new connections to be established. The client then requests whatever data and the connection is closed, the child dies, and the port is released back to the assignable pool.
I'm not a TCP/IP "engineer" or one of those liberal elite "computer scientists" but this is the general idea. <http://infolab.stanford.edu/CHAIMS/Code/Wrappers/TCPIP_CPAM/webpage/TCPIP.html> Scott On Tue, Oct 27, 2009 at 8:11 PM, Joe Reichman <joereich...@optonline.net>wrote: > Hi, > > > > All regarding my earlier inquiry can anyone correct me if I am wrong > > > > I don't think you can have multiple open connections ( in the process of > read and writes ) on the same port/same ip ?? > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
