Re: NSURLConnection Latency on iPhone
Re: NSURLConnection Latency on iPhone
- Subject: Re: NSURLConnection Latency on iPhone
- From: Josh Graessley <email@hidden>
- Date: Mon, 29 Dec 2008 15:38:05 -0800
On Dec 28, 2008, at 7:00 PM, Matthew Rushton wrote:
After more time on this the issue is 100% latency on the wireless
network. On the iPhone using NSURLConnection for any performance
based networking is not going to work well at least not without
accommodations (for example doing some snooping showed that the
native maps app requests multiple tiles with each request and not
one at a time sequentially). I've looked in to using CFHttpStream to
try and get http pipelining to work (which would solve my problem)
but the documentation was lacking and it's unclear what exactly the
behavior is and/or if it can change between releases. I have no
desire to handle http connections myself to get pipelining to work
either. So unless anyone has any other ideas or has had success with
http pipelining using a relatively simple solution I think I'm going
back to my more light weight custom tcp proto that does pipelining
rather than using http requests. That's it!
-Matt
Pipelining can solve your problems but you would have to roll your own
http client code. To the best of my knowledge, pipelining isn't
automatically enabled in the frameworks because it doesn't work in all
situations. As it was explained to me a variety of things can screw up
pipelining from HTTP proxies to various apache plug-ins. This is a
shame because the browsing performance over the cellular network is
severely limited by latency, not bandwidth. It's frustrating to watch
the carriers tote faster and faster speeds without any mention of
latency when high latency is really what makes cellular internet a
painful slow experience.
-josh
_______________________________________________
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