Re: Unbinding an endpoint in OT when running in Classic -- solved.
Re: Unbinding an endpoint in OT when running in Classic -- solved.
- Subject: Re: Unbinding an endpoint in OT when running in Classic -- solved.
- From: Quinn <email@hidden>
- Date: Mon, 19 Apr 2004 09:46:55 +0100
At 15:13 -0700 15/4/04, Justin Walker wrote:
Typically, and I believe OT uses this convention, a bind() with a
zero port tells the kernel (or the port-assigner) that it should
allocate an unused port in what's called the "ephemeral range" (the
high end of the port number space). That way, your app will not
have to scan for an unused port.
Yep. You can discover the port that actually was used by passing
TBind to the retAddr parameter of OTBind.
Passing 0 to the port number of a bind request is both legal and, in
many cases, the correct behaviour. I have no idea why it would cause
port reuse problems. I'd appreciate it if you could file a bug
report, including a copy of your tiny test program.
<
http://developer.apple.com/bugreporter/>
S+E
--
Quinn "The Eskimo!" <
http://www.apple.com/developer/>
Apple Developer Technical Support * Networking, Communications, Hardware
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.