Re: Does CFSocket use efficient polling?
Re: Does CFSocket use efficient polling?
- Subject: Re: Does CFSocket use efficient polling?
- From: Ladd Van Tol <email@hidden>
- Date: Fri, 13 Feb 2009 19:25:32 -0800
On Feb 13, 2009, at 4:41 PM, Jeremy Wyld wrote:
Unless it's super huge! That does very bad things on the Phone.
Yes, the memory limits are never far from our minds. We are actually
dealing with much smaller transactions on the phone (200K max), but it
was easier to measure larger transfers.
Also the speed tests aren't great. Using a 50MB file on a giga link
is really showing burst speeds. That number is important, and in
this case, he was trying to show CPU usage. Larger downloads should
be used for throughput comparisons.
For my specific uses on the iPhone, throughput is less important than
CPU usage. Even a 400 MHz processor should be able to deal with
comparatively pokey 3G network speeds.
Mac numbers are shown mostly for illustrative purposes, although the
same inefficiencies apply to real world Mac apps as well.
Mark, also, was good to point out comparing NSURLConnection is not
the best comparison as it has yet another layer over CFStream which
is a layer over CFSocket which was being questioned in the first
place.
I'll definitely try the low-level APIs, but there's really not a good
reason for such a huge performance penalty in the high level APIs over
something like libcurl.
Admitted, it is synchronous, and somewhat difficult to use, but
libcurl offers good performance and a generally better feature set
than the Apple HTTP APIs.
- Ladd
_______________________________________________
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