[squeak-dev] Closing a socket for port re-use - dumb question

Bill Schwab BSchwab at anest.ufl.edu
Fri Feb 29 18:10:03 UTC 2008


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 socket
such that same service could be restarted on the same port.  There must
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/stop
of a Seaside server could be a nice place to start to verify that it is
not a problem.  However, I would ideally like to understand the problem
so I won't walk into it again.  Perhaps it was just a Windows bug???

Thanks,

Bill




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 mailing list