• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: CURL and Connection limits
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CURL and Connection limits


  • Subject: Re: CURL and Connection limits
  • From: Murat Konar <email@hidden>
  • Date: Mon, 17 Sep 2007 12:53:09 -0700

I don't claim that our problems are the same, but I offer my experiences as a data point.

This sounds sort of like a problem I've run into in the past when connecting to a Yahoo (including Geocites) server. Something about the way they're configured makes using CURL to access them hard to do properly.

Performing one operation per event loop seems to help. Presumably, when the pools are drained at the end of a run loop, some under the hood curl stuff gets cleaned up.

Another frustrating thing about the Yahoo/Geocities FTP servers is that you must space your operations (by "operation" I mean a single curl perform call) some small amount of time (on the order of 3 seconds or so) apart or the server will reject your login something like 25% of the time.

It's a pain in the butt.

Sorry for the fuzzy/vague info. It was a while ago, and I don't have my sources handy.

_murat


On Sep 17, 2007, at 12:17 PM, Jofell Gallardo wrote:

I'm currently using libcurl.framework for an app I'm making, and it was a
bit weird that I get these behaviors.
First off, I always get error messages saying that I can't connect to the
server in FTP, and when I do verbose
logging, it shows that I get the error *after* a change working directory
command (CWD) inside it. What's more
interesting is that I also get these errors on the 230th to 234th item,
that's why a guy from the libcurl mailing
list told me it could my workspace running out of file handles /
descriptors. Another thing is that it also affects
all my NSURLRequest calls, and they also have errors similar to the libcurl
library I made: can't connect to
server.


Surely, I checked if I closed my file handles and curl connections, which
led me to get away from any
NSURLRequest instantiation and use libcurl for me to force the closing of a
connection. Unfortunately, the
problem still persists.


Any help or suggestion will be appreciated.
_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: CURL and Connection limits
      • From: "Jofell Gallardo" <email@hidden>
References: 
 >CURL and Connection limits (From: "Jofell Gallardo" <email@hidden>)

  • Prev by Date: CURL and Connection limits
  • Next by Date: Re: Capturing the right display, but rendering to the wrong one.
  • Previous by thread: CURL and Connection limits
  • Next by thread: Re: CURL and Connection limits
  • Index(es):
    • Date
    • Thread