title: Good design patterns for coding many HTTP requests in Android
body: <p>In my app, i have lots of GET,POST, PUT requests. Right now, i have a singleton class that holds my downloaded data and has many inner classes that extend AsyncTask. 
  In my singleton class, i have also a few interfaces like this:</p>
  
  <pre><code>/**
  * Handlers for notifying listeners when data is downloaded
  * 
  */
  public interface OnQuestionsLoadedListener {
  
      public void onDataLoadComplete();
  
      public void onDataLoadingError();       
  }
  </code></pre>
  
  <p>Is there something wrong with this pattern (many inner classes that extend AsyncTask)? 
  Could it be done more efficiently with maybe just 1 inner class for every HTTP call (1 for GET, 1 for POST, ...)? If so, how to decide what to do after e.g. GET request?</p>