Re: socket() returning same value in shared library ( wasRe:accept() hangs)
Re: socket() returning same value in shared library ( wasRe:accept() hangs)
- Subject: Re: socket() returning same value in shared library ( wasRe:accept() hangs)
- From: "Justin C. Walker" <email@hidden>
- Date: Mon, 10 Oct 2005 13:47:16 -0700
Thanks for the details. See below...
On Oct 10, 2005, at 13:26 , Ken Baer wrote:
On Oct 10, 2005, at 11:54 AM, Justin C. Walker wrote:
On Oct 10, 2005, at 11:29 , Ken Baer wrote:
[snip]
Yeesh! That's a twisty maze of passages...
As indicated earlier in this thread, the value 42 may be a red
herring.
OK, but what about the socket I am supposed to get back from accept
()? It would be the same number as the listening socket.
On this last comment, No: the accept() call takes the listening
socket descriptor and returns a brand-spanking-new socket descriptor
for your use.
At this point, I am unclear as to what is going on, since it appears
to have more to do with your design and your use of the CFSocket
stuff. Since I'm not an expert in the latter framework, I'll let
others fill in the blanks.
Regards,
Justin
--
Justin C. Walker, Curmudgeon-At-Large
Institute for General Semantics
--------
"Weaseling out of things is what separates us from the animals.
Well, except the weasel."
- Homer J Simpson
--------
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden