My first suggestion would be to take a close look at
TCPServer.m and
see where you can spin off a new thread for each
request.
TCPServerAcceptCallBack() looks like a good
candidate.
I agree that this is the right place, but I'm stumped.
I don't mean to be dense but I don't see any way to
convert this into something I can pass into NSThread's
detachNewThreadSelector.
Also, I don't think that responding in a separate
thread is what I need, since I really want it to
listen for connections in a separate thread; to make
the entire TCPServer class run in its own thread.
You can listen to connections in a separate thread and handle them in
that same thread. What you do is, you start the new thread and create
all your server-related objects in that thread, and call all the read/
write methods in that thread as well.
If the main thread wants to interact with the remote apps in any way,
you'll need to use some sort of system to pass data or commands back
and forth from the server thread. See my response to the "passing
data to threads" message.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
