Re: NSURLConnection not reentrant?
Re: NSURLConnection not reentrant?
- Subject: Re: NSURLConnection not reentrant?
- From: Jerry Krinock <email@hidden>
- Date: Mon, 21 Nov 2005 16:06:11 -0800
- Thread-topic: NSURLConnection not reentrant?
on 05/11/21 11:15, Ed Voas at email@hidden wrote:
> I can't see anything in the docs about this, but we have a situation
> where in the connectionDidFinishLoading callback we are starting another
> fetch using another connection. This second fetch just hangs and never
> completes. I'm guessing that NSURLConnection won't call a delegate (or
> perhaps even start the fetch) when it's already calling another one.
To start "another fetch using another connection", you should create another
NSURLConnection.
> Is
> this the case? If so, I'll need to manage my own completion queue, which
> I was hoping I didn't need to do on Mac.
In the "Class Description" of the NSURLConnection documentation:
Unless a NSURLConnection receives a cancel message, the delegate will
receive one and only one of connectionDidFinishLoading:, or
connection:didFailWithError: message, but never both. In addition, once
either of messages are sent, the delegate will receive no further messages
for the given NSURLConnection.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden