Best practice to send a lot of data in background on iOS4 device?

Question

I have an app that needs to send date (using POST) to a server. This function has to be on one of the NavigationController sub-controllers and user should be able to navigate away from this controller and/of close the app (only iPhone4/iOS4 will be supported). Should I use threads/NSOperations or/and send data using existing asynchronous methods? Any ideas/best practices how to implement this?

Answer 1

I'd definitely suggest a second thread for any long running process which need to run whilst the user is doing something else.

Another thing you will need to think about is what is going to happen if the user starts the process and then hits the home button. How will the server interaction be effected by being interrupted? Can it continue when the user next enters the app? etc.

Answer 2

Use ASIHTTP and setup a Queue. All the information you need can be found here:

http://allseeing-i.com/ASIHTTPRequest/

This is the easiest way to accomplish what you want to accomplish. For sending lots of data, it is better to send in the background to keep the UI responsive. ASIHTTPRequest provides all the methods you need to kick of multiple queries (i.e. progress checks, callbacks, etc).

It's used by tons of great iPhone apps.

Answer 3

I'd just use NSURLConnection. It's a bit tricky if you want to send multipart/form-data (see the SimpleURLConnections/PostController.m example). I'd stick it in the app delegate, but I'm lazy like that.

You shouldn't worry about threads at all unless non-blocking I/O (i.e. NSURLConnection) is too slow. Threading has its own overheads, and inter-thread communication is a pain, and deadlocks are terrible.

What you do need to do is start a background task to allow your app to continue executing while backgrounded (end the background task in connectionDidFinishLoading: and connection:didFailWithError). Backgrounded apps are given about 10 minutes to finish executing background tasks.

Answer 4

OK, I'll answer my own question. First, like tc said, it's better to have this call on the application delegate, so that the View in the NavigationController can be closed. Second, mark beginning of the background processing with beginBackgroundTaskWithExpirationHandler: and end it with endBackgroundTask: like this:

.h:

UIBackgroundTaskIdentifier bgTask;

.m:

- (void)sendPhoto:(UIImage *)image
{
  UIApplication *app = [UIApplication sharedApplication];

  bgTask = [app beginBackgroundTaskWithExpirationHandler:^{ 
    [app endBackgroundTask:bgTask]; 
    bgTask = UIBackgroundTaskInvalid;
  }];


  NSLog(@"Sending picture...");

  // Init async NSURLConnection

  // ....
}

- (void)connectionDidFinishLoading:(NSURLConnection *)connection {

  NSLog(@"Picture sent.");

  UIApplication *app = [UIApplication sharedApplication];

  if (bgTask != UIBackgroundTaskInvalid) {
    [app endBackgroundTask:bgTask]; 
    bgTask = UIBackgroundTaskInvalid;
  }
}

You have 10 minutes before iOS terminates your app. You can check this time with [app backgroundTimeRemaining]

Answer 5

I'd like to support the post that mentions:

bgTask = [app beginBackgroundTaskWithExpirationHandler:^{

 [app endBackgroundTask:bgTask]; 

 bgTask = UIBackgroundTaskInvalid;

}];

But also point out that you may want to encapsulate your unit of work in an NSOperation subclass as well. This will make it extremely re-useable and, when combined with NSOperationQueue, automatically handle threading and what not. Then later, when you want to change your code, or have it appear in a different location in your app, it will be trivial to move or edit.

One note about using the operation queue, is that in this case you will actually want to send a synchronous url request from within the queue. This will let you not have to worry about concurrent operations. Here is the link that you may find helpful:

http://www.cimgf.com/2008/02/16/cocoa-tutorial-nsoperation-and-nsoperationqueue/