Indeed, TIME_WAIT is there for a reason, but SO_REUSEADDR does not (or
at least should not) short-circuit TIME_WAIT or any other state. What
it does is allow an application to have a new instance of its LISTEN
endpoint while there are still previous connections in states "beyond"
the LISTEN state.
rick jones
--
Wisdom Teeth are impacted, people are affected by the effects of events.
these opinions are mine, all mine; HP might not want them anyway... :)
feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...