As far as I know, every OS out there has a primitives, available to
programs through a socket library, which choose the "ephemeral" port
for the client side of the binding when a client opens a TCP
connection, cycling through the high range of numbers designated for
that on each new connection request. It is unlikely that your browser
is getting one of the low reserved numbers for its binding. More
likely is that one of your custom applications has "reserved"
something in the ephemeral range. That can work ok, as long as your
custom application starts early enough to get its port bound before
it's given out for some other purpose.
Walden
> > Ted- Hide quoted text -
>
> - Show quoted text -