Re: CFHTTPMessage and thread safety
Re: CFHTTPMessage and thread safety
- Subject: Re: CFHTTPMessage and thread safety
- From: Mark Pauley <email@hidden>
- Date: Fri, 29 Aug 2008 12:28:42 -0700
Sorry, that should have been:
spawn a bunch of threads, each thread creates a message / http stream and sets the Persistent Connection property on its stream. Then we schedule on the current RunLoop,
Call CFReadStreamOpen on this thread's ReadStream
run the current RunLoop and handle the callbacks, unschedule the ReadStream and join the thread when the download is finished. What is your usage pattern?
If you decide to not schedule the streams, you'll get synchronous behavior per-thread which is similar to a lot of the Java networking patterns I've seen.
_Mark
email@hidden
|
_______________________________________________
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