Handling orientation changes yourself
<p>From the documentation regarding the <code>android:configChanges='orientation'</code> attribute of the activity tag in the manifest:</p>

<blockquote>
  <p>Note: Using this attribute should be avoided and used only as a last-resort. Please read Handling Runtime Changes for more information about how to properly handle a restart due to a configuration change.</p>
</blockquote>

<p>Why does it say this?  </p>

<p>In the case of threads and networking requests via a service API library, a request could be made with a reference to the original Activity, and then an orientation change could occur, leaving the thread pointing to the old Activity.</p>

<p>While this can be fixed, it's tedious and ugly compared to just handling the configuration changes yourself.</p>

<p>Why should it be avoided?</p>

<p>Edit:  I guess I should also ask: would this be an acceptable reason for doing the orientation configuration changes yourself?</p>
