nsurlconnection

I am curious about 2 things: 1 whats the efficient and easy-to-scale way to design communication between object that communicates with API and viewcontrollers 2 how to design the communicating object itself (how to design methods to be scalable,..) (My approach mention below is messy, I know, but the deadlines were crazy and until now I didn't have time to think about it really.) Let me introduce the task I was dealing with: I had to write 2-3 apps depending on communication with API. There was about 10-15 different methods that the API responded to (send via http POST, result in JSON). Of

I am downloading a bunch of largish zip files with the following method. It can take a little while and so I'd like to display a progress bar. I've researched how to do with with the delegate methods for NSURLConnection and it seems straightforward, however I want to achieve the same thing with "sendAsynchronousRequest". How can I get the number of bytes downloaded as it downloads as well as the total number of bytes expected so that I can display a progress bar? I understand that I cannot use the delegate methods if I kick off a download in the manner I am doing it. // Begin the download

I am connecting to server using NSURLConnection . The server asks for basic authentication for which I am using the delegate methods :- didReceiveAuthenticationChallenge . But this gets called only once. If I change password to some different value, then this delegate methods does not get called and it takes my login as successful? Any kind of help will be appreciated. Thanks. Solved! It turns out that NSURLConnection was actually behaving correctly - that is, didReceiveAuthenticationChallenge: was being called for every authentication challenge. The problem was that the server was not sending

What does a web service need to do to cause NSURLConnection's delegate to receive the connection:didFailWithError: message? For example: iOS app passes a token to the web service, web service looks up the token, and then the web service needs to respond with an error saying "invalid token" or something of the like. Currently, the data is received, and in " connectionDidFinishLoading :" is parsed for error messages. This means I'm error checking in two places, which I am trying to avoid. I have both the iOS app and web service completely under my control. In my experience (the three most

I'm trying to find a definitive answer to if it possible to set the timeout value for using NSURLConnection in iOS 5 (I would like to set it to 30 seconds). I've searched past postings on this but the information seems contradictory. For example, this posting NSURLConnection timeout? says Apple mandates a 4 minute minimum timeout - though I cannot find any Apple documentation to support this. THis posting says the 240 limit comes from an apple forum thread NSMutableURLRequest not obeying my timeoutInterval They say this limit is only for POSTs when the body isn't empty. Does that imply its

My iOS app is getting the code inside (ex. 101), and by that code it reads JSON file (ex. 101.json) on server and read the data inside. Everything is working good, but how to do that if there's no file (for that code) on server (now it's just showing no data if file not found) and if there's no internet connection just to get data from JSON file inside the app? Here's my code: NSString *baseURLStr = @"http://myserverurl/"; NSURLRequest *request = [NSURLRequest requestWithURL:[NSURL URLWithString:[baseURLStr stringByAppendingFormat:@"%d/%d.json", int1, int2]]]; NSData *data = [NSURLConnection

Closed. This question is off-topic. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 3 years ago . I would like to receive Server-Sent Events in my native iOS app however am not using webkit/Safari. From what I've found, NSURLConnection is poor fit as it chunks response . I've also looked at ZTWebSocket library (obviously nice, but I'm seeking SSE, not web sockets). Would CocoaAsyncSocket be appropriate? Or limited to pure TCP Socket communication? I have a sneaking suspicion that I am missing