[squeak-dev] Closing a socket for port re-use - dumb question
Randal L. Schwartz
merlyn at stonehenge.com
Fri Feb 29 18:54:07 UTC 2008
Not sure in the windows world, but by design, sockets closed are held
closed for two minutes in case late packets arrive. If you don't care
about that you can set "socket reuse" on the socket before you close it.
Pardon me if this is brief, but I'm sending this from my iPhone!
On Feb 29, 2008, at 10:10 AM, "Bill Schwab" <BSchwab at anest.ufl.edu>
> Hello all,
> Slightly OT, except that I am asking for the potential benefit of
> Squeak. Several years ago, I had problems with closing a server
> such that same service could be restarted on the same port. There
> be a correct way to do this (too many products do it successfully
> for it
> to be a problem), but at the time I was told that ephemeral
> ("dynamically allocated") ports were the best solution. I got it
> working, but have regretted it due to fire walls and other criteria.
> Can anyone point me to what I might have been doing wrong, and/or an
> example of how to do it correctly? Of course, stress testing start/
> of a Seaside server could be a nice place to start to verify that it
> not a problem. However, I would ideally like to understand the
> so I won't walk into it again. Perhaps it was just a Windows bug???
> Wilhelm K. Schwab, Ph.D.
> University of Florida
> Department of Anesthesiology
> PO Box 100254
> Gainesville, FL 32610-0254
> Email: bschwab at anest.ufl.edu
> Tel: (352) 846-1285
> FAX: (352) 392-7029
More information about the Squeak-dev