Re: Inappropriate NSError from -[NSURLConnection sendSynchronousRequest:::]
Re: Inappropriate NSError from -[NSURLConnection sendSynchronousRequest:::]
- Subject: Re: Inappropriate NSError from -[NSURLConnection sendSynchronousRequest:::]
- From: Mark Pauley <email@hidden>
- Date: Wed, 7 Oct 2009 17:15:23 -0700
You might want to consider just using an NSRunLoopSource instead of a
separate thread that blocks on a lock.
And, actually you may not even need to do that if you are willing to
just make your delegate's didFinish callback initiate whatever action
you need to finish after the response is complete.
On Oct 5, 2009, at 4:45 PM, Jerry Krinock wrote:
On 2009 Oct 04, at 22:44, Jeff Johnson wrote:
Don't use +[NSURLConnection
sendSynchronousRequest:returningResponse:error:], it's a bad API....
Yes, I see what you mean, Jeff. This API is a handy shortcut which
may be OK for talking to your own server, but its behavior is not
documented well enough to predictably handle the Real World with all
of its corner cases.
So I'll have to bite the bullet -- implement a delegate and a thread-
block/lock.
_______________________________________________
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
_Mark
email@hidden
_______________________________________________
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