If the NSURLConnection in question has been started asynchronously, your
described scenario sounds appropriate. In fact, it's what Apple recommends
since the class will handle things in the background and only report back on
progress. A synchronous request would fall into the questionable realm.
I'm looking at some Cocoa spaghetti that seems to violate all the laws or
reason and I'd just appreciate some verification that "there is no reason
whatsoever that a sane Cocoa developer would ever do this" before I go and
change this code.
Am I correct in assuming that there is no rational rea
