At the server side, we use
Socket server = serverSocket.accept();
to create a socket. After the socket is created, we can create a new thread to handle the input/output stream of that socket. So we can go back to listening at the same port and create new socket if there are further connection requests come in. Since we already created ServerSocket at a specific port, of course we could not create another ServerSocket at that port again.
So from my understanding, can I conclude that, at server side, we can create multiple sockets under one port? (similar to what web server does)
Actually my question is, at client side, when we are creating a socket, we can specify the local port that we want to use. After we have successful created a client socket at that local port, can we reuse that port for other client socket? Does that port bind to the socket permenantly until the socket is closed (or port close)? Since there is no "Listening" concept at client side, are we able to do the same thing as ServerSocket does (refer to ServerSocket can create multiple socket under one port)?
I am seriously confused how client side handle the port and socket, because I am comparing ServerSocket with the client socket.
Please point me to the correct direction, I know that my thinking somehow is wrong. Thanks very much.
So from my understanding, can I conclude that, at server side, we can create multiple sockets under one port? (similar to what web server does)
You're confusing yourself with your terminology. ServerSocket.accept() accepts a connection, and wraps the endpoint in a Socket. The endpoint has the same local port number as the ServerSocket, by definition as per RFC 793, and therefore so does the wrapping Socket.
Actually my question is, at client side, when we are creating a socket, we can specify the local port that we want to use.
We can, but we rarely if ever do so.
After we have successful created a client socket at that local port, can we reuse that port for other client socket?
No.
Does that port bind to the socket permenantly until the socket is closed (or port close)?
Yes, or rather the other way round: the socket is bound to the port.
Since there is no "Listening" concept at client side, are we able to do the same thing as ServerSocket does (refer to ServerSocket can create multiple socket under one port)?
No.