| |||
| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
On Dec 15, 2005, at 12:49 AM, Alexey Proskuryakov wrote:
If you use libcurl instead of Apple's code you lose the runloop integration, and perhaps more importantly you lose the confidence that your app will behave "at least as well as Safari." It sounds like you've had some bad luck with Safari, but I have found it pretty reliable. I use libcurl for some projects but when possible I use CFNetwork because of the consistent CoreFoundation interface, and because I know that a bug in CFNetwork that affects my application is also probably a bug in Safari, and will therefore be taken seriously. One big advantage to using libcurl is that if you find a bug, you can fix it yourself and link in a private copy of the library pretty easily. Since CFNetwork sources have recently been released by Apple, this is true there as well, but I don't think it's easy to build it as a static library "out of the box," and I'm not sure what the ramifications of including a private copy of CFNetwork.framework in your application's bundle would be. Daniel |
_______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/macnetworkprog/email@hidden This email sent to email@hidden
| References: | |
| >Re: URLAccess Stalls (From: Alexey Proskuryakov <email@hidden>) | |
| >Re: URLAccess Stalls (From: Marc Krochmal <email@hidden>) | |
| >Re: URLAccess Stalls (From: email@hidden) | |
| >Re: URLAccess Stalls (From: Marc Krochmal <email@hidden>) | |
| >Re: URLAccess Stalls (From: "Alexey Proskuryakov" <email@hidden>) |
| Home | Archives | FAQ | Terms/Conditions | Contact | RSS | Lists | About |
Visit the Apple Store online or at retail locations.
1-800-MY-APPLE
Contact Apple | Terms of Use | Privacy Policy
Copyright © 2007 Apple Inc. All rights reserved.