When a TCP/IP connection is terminated with an orderly CLOSE (FIN, FIN-ACK, ACK), the application that initiated the CLOSE is not notified that the connection is CLOSED until the TIME-WAIT timeout expires. On an MCP system, prior to MCP Networking release 57.1 (16.0), this caused a 2 second delay before the application could proceed, which was a performance issue for programs that opened and closed many files. As of MCP Networking release 57.1 (16.0), the application is notified that the connection is closed when the TCP/IP state is changed to Time-Wait.
| Note: | An application cannot open a new connection with the identical addressing, that is, the same MyIPAddress/YourIPAddress and MyName/YourName pairing, until the Time-Wait state has ended. An attempt to open a connection before that time will result in an open error. The errorcode returned will be dependent on the programming interface used (Error 246 = ConnectionInUse if using TCPIPNATIVESERVICE Port files or Error -56 EisConn if using BSD Sockets). |
