Re: NSMutableURLRequest: Keeping the connection open
Re: NSMutableURLRequest: Keeping the connection open
- Subject: Re: NSMutableURLRequest: Keeping the connection open
- From: Thomas Engelmeier <email@hidden>
- Date: Wed, 30 Mar 2011 20:19:37 +0200
On 30.03.2011, at 20:06, Mark Pauley wrote:
> NSURLConnection closes sockets after a relatively short period in order to allow the system to power the antenna down more quickly, thus saving battery life.
That's what I suspected..
> If you absolutely must know about the underlying connections or if your app is hitting a pathologically bad case of socket management, feel free to drop down to CFHTTPReadStream, otherwise I would recommend that you not worry about the details of socket connections and just use NSURLConnection as is.
> If you do decide to use CFHTTPReadStream: make sure you don't close the stream until after you open the next stream. This is how you can keep the underlying socket open. Also be advised that you only get one socket per host / port pair going that route unless you want to get more tricky.
OK, I'll give it a try. Does the later mean I can run into big trouble (i.e. lenghty timeouts) with interrupted and re-established internet access and I'll have to carefully adjust and test the code for reachability transition corner cases?
TIA,
Tom_E
_______________________________________________
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