🚀 go-pugleaf

In article <3vo653$ahi@inforamp.net>,
Kevin Rosenthall <Kevin.Rosenthall@PoBox.Com> wrote:
>When you create a socket, the system (or TCP/IP stack) gives you a
>socket descriptor number, e.g. 26.  Now, if I close socket 26, and
>request a new socket, rather than getting 26 again, the system gives
>me socket 27.  It would appear that the system is not very good at
>recycling old sockets.

Kevin -

I don't think that this behavior demonstrates any lack of efficiency.  
I'm pretty sure that when a socket is closed, its resources (memory) are 
freed, even though the number isn't immediately reused.

Incrementing the number has an advantage over immediately reusing it:  If
you've passed the socket handle to another thread, etc., and the socket
has been closed, then a call with that socket handle will fail.  This is
as it should be.  Otherwise, the call would succeed even though it
referred to a socket different from the intended one. 

- Keith

-- 
--------------------------------------------------------------------------
Keith Bennett                             Bennett Business Solutions, Inc.
Silver Spring, MD USA                     OS/2 & DOS Software Development
kbennett@cpcug.org                        (301) 871-7696