title: Risks of using performSelectorInBackground?
body: <p>I have been doing some testing with <a href="http://iphoneonrails.com/" rel="nofollow">ObjectiveResource</a> (iOS->Rails bridge). Things seem to work, but the library is synchronous (or maybe not, but <a href="http://groups.google.com/group/objectiveresource/browse_thread/thread/6f05ed9f4df0c3ba/9fdd338d72ef9c33?lnk=gst&amp;q=async#9fdd338d72ef9c33" rel="nofollow">the mailing list that supports it is a mess</a>).</p>
  
  <p><strong>I'm wondering what the pitfalls are to just running all calls in a <code>performSelectorInBackground</code></strong>... in small tests it seems to work fine, but that's the case with many things that are wrong.</p>
  
  <p>The only caveat I've noticed is that you have to create an Autorelease Pool in the method called by performSelectorInBackground (and then you should only call <code>drain</code> and not <code>release</code>?).</p>