On Dec 14, 2005, at 9:49 PM, Alexey Proskuryakov wrote:
On Wed, 14 Dec 2005 16:55:39 -0800 Marc Krochmal <email@hidden>
wrote:
Practically every application Apple ships, including Safari, uses
non- blocking IO. The fact that Safari shows the spinning beach
ball sometimes is not related to this, and is probably caused by
a bug.
The URLAccess API was designed for a different time. It uses
Thread Manager, FSSpecs, Pascal strings, and other Mac OS 9 isms
and didn't fit Apple's future direction of using CoreFoundation
types and RunLoops.
Ability to use CFStrings for server names is just so exciting...
Er, I mean useless. And URL Access callbacks are conceptually
similar to CF run loops, so I'm pretty sure it wouldn't have been
too hard to develop a wrapper.
Water under the bridge now...
There were other reasons to deprecate URL Access besides the three I
listed. Those were just some examples.
We highly encourage you to make the transition to CFNetwork.
I'm very interested in your opinion about libcurl. I haven't used
it as a library yet, but from a user's standpoint, curl is
significantly more polished and reliable than CFNetwork, and
isolates one from Apple's "future direction" du jour.
I really don't have an opinion on libcurl since I've never used it,
but, avoiding Apple APIs because they might get deprecated in the
future is probably not a good strategy.
Yesterday I was downloading InDesign 4.0.2 update from Adobe
site, and Safari failed several times (it would start, but finished
the download with an incomplete file of 4-5 megabytes instead of 30
+, yet no indication of error). Sure, curl from command-line saved
the day, just like many times before :-(
I just tried downloading the file but did not experience any
problems. Here's a link in case anyone else wants to try downloading
it...
