Question

Long time reader, first time poster here.

I’m creating a test app that creates a NSURLConnection and then displays the result on an UILabel.

I am presently using a Notification Center observer, which fires a notification from within connectionDidFinishLoading to wait for the connection to complete successfully, before I look for the result.

However, what I am struggling to conceptualize is where to store the response data so that I can access it from my View Controller and post the result to the UILabel. (Or from anywhere other than an instance of my Connection Class, for that matter.)

I don’t want to post directly to the UILabel from connectionDidFinishLoading. I need a way to decide what I will do with the response later – so my Connection Class stays generalized.

I need a better way to save the response data somewhere, where I can reference it after the instance of the Connection Class has terminated.

Ideally, it should be somewhere that I can have multiple instances of the Connection Class open, and access each response in turn as I need them. This eliminates the potential to just create a variable in my View Controller or somewhere else more global and dump the response to it.

Any ideas on what design patterns could/should be used here would be greatly appreciated!

Answer 1

My suggestions for you to start with are :

1. Make a singleton class. I will have a property NSDictionary * info or NSArray *infoList; You will have acces to the same data from wherever the app. Update the property, post the notification, access the property from the viewController.
2. Store the info into a plist/file. Serialize the information, or save plain stream. Whatever you like.Thus after you finish writing to the file, post the notification, read from the file from anyplace within the app.

In both cases if you want multiple connections i suggest going for the factory design Pattern.