title: iOS, Objective C - NSURLConnection and asynchronious examples, default behavior and best practices?
body: <p>I have been working with a few applications that deal with NSURLConnections. While researching best practices I have noticed a lot of examples online showing how to use <code>NSOperation</code> and <code>NSOperationQueue</code> to deal with this. </p>
  
  <p>I have also noticed on stackoverflow a few examples that show initializing the connection as synchronous and asynchronous using the class methods of <code>NSURLConnection</code>: <code>sendAsynchronousRequest</code> and <code>sendSynchronousRequest</code>.</p>
  
  <p>Currently I am doing my initialization as follows:</p>
  
  <pre><code>[[NSURLConnection alloc] initWithRequest:request delegate:self];
  </code></pre>
  
  <p>While doing this I have monitored the main thread and the calls to the delegate methods:</p>
  
  <p><code>connectionDidFinishLoading</code>, <code>connectionDidReceiveResponse</code>, <code>connectionDidReceiveData</code> and <code>connectionDidFailWithError</code></p>
  
  <p>Everything I have read in Apples documentation and my tests prove to me that this is asynchronous by default behavior.</p>
  
  <p>I would like to know from more experienced Objective C programmers when the other options would be used for either a best practice, or just be more correct than what I see as the most simplistic way to get async behavior?</p>
  
  <p>This is my first question I have posted on here, if more information is needed please ask. </p>