Re: URLAccess Stalls
Re: URLAccess Stalls
- Subject: Re: URLAccess Stalls
- From: "Alexey Proskuryakov" <email@hidden>
- Date: Thu, 15 Dec 2005 08:49:34 +0300
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.
Indeed, see <http://bugzilla.opendarwin.org/show_bug.cgi?id=5633>. After
this one is committed, one may want to use nightly builds from
<http://nightly.webkit.org>, and file bugs for remaining lockups (using Spin
Control, for example).
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...
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.
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 :-(
- WBR, Alexey Proskuryakov
_______________________________________________
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