title: Google Volley vs Android-Async-Http
body: <p>I am looking into both these Android Http Networking libraries.</p>
  
  <p>I would like some peoples experiences with using the two libraries. Personally I have always used the <a href="http://loopj.com/android-async-http/">http://loopj.com/android-async-http/</a> library quite happily. But it was recently suggested to me to use the Volley Framework.</p>
  
  <p>What benefits will I get from one over the other?<br>
  From my reading so far, Volley incorporates a number of nice features such as Image Loading, Request Caching, Request Cancelling all in one library.</p>
  
  <p>My current use case / specifications:</p>
  
  <p>Consume web services from my android applications.</p>
  
  <ul>
  <li>Receive JSON Objects from web service</li>
  <li>Easy To integrate with the GUI</li>
  <li>Stability and Reliability over raw performance</li>
  <li>Long term maintenance and support of the library.</li>
  <li>Ease of use / ease of implementation</li>
  </ul>
  
  <p>From some reading up on SE:</p>
  
  <p>"Volley is all good but, On the minus side, it is one undocumented, unsupported, "throw the code over the wall and do an I|O presentation on it" library."</p>
  
  <p>So I think its clear Volley might get the tick for features, But how well documented and maintained is it? If I decide to use it will there still be support for it 4 years down the line?</p>