resolved conflicts for d32f3baf to mnc-mr-docs

<div class="landing-docs">

  <div class="col-6">

    <h3>Blog Articles</h3>

    <a href="http://android-developers.blogspot.com/2011/09/androids-http-clients.html">

      <h4>Android’s HTTP Clients</h4>

      <p>Most network-connected Android apps will use HTTP to send and receive data. Android

includes two HTTP clients: HttpURLConnection and Apache HTTP Client. Both support HTTPS, streaming

uploads and downloads, configurable timeouts, IPv6 and connection pooling.</p>

    </a>

  </div>

  <div class="col-6">

  <div>

    <h3>Training</h3>

    <a href="http://developer.android.com/training/efficient-downloads/index.html">

      their data when recovering from a data loss (such as a factory reset) or installing your

      application on a new device.

      </p>

    </a>

  </div>

hostname to the server so the proper certificate can be returned.</p>

<p>Fortunately, {@link javax.net.ssl.HttpsURLConnection} supports

SNI since Android 2.3. Unfortunately, Apache

HTTP Client does not, which is one of the many reasons we discourage its use. One workaround

if you need to support Android 2.2 (and older) or Apache HTTP Client is to set up an alternative

SNI since Android 2.3. One workaround

if you need to support Android 2.2 (and older) is to set up an alternative

virtual host on a unique port so that it's unambiguous which server certificate to return.</p>

<p>The more drastic alternative is to replace {@link javax.net.ssl.HostnameVerifier}

<h2 id="http-client">Choose an HTTP Client</h2>

<p>Most network-connected Android apps  use HTTP to send and receive  data.

Android includes two HTTP clients: {@link java.net.HttpURLConnection} and the Apache HTTP client.

Both support HTTPS, streaming uploads and downloads,  configurable

timeouts, IPv6, and connection pooling. We recommend using {@link

java.net.HttpURLConnection} for applications targeted at Gingerbread and higher. For

more discussion of this topic, see the blog post <a

href="http://android-developers.blogspot.com/2011/09/androids-http-clients.html"

>Android's HTTP Clients</a>.</p>

<p>Most network-connected Android apps use HTTP to send and receive data. The

Android platform includes the {@link java.net.HttpURLConnection} client, which

supports HTTPS, streaming uploads and downloads, configurable timeouts,

IPv6, and connection pooling.</p>

<h2 id="connection">Check the Network Connection</h2>

of the requests, and a cache to handle caching. There are standard implementations of these

available in the Volley toolbox: {@code DiskBasedCache} provides a one-file-per-response

cache with an in-memory index, and {@code BasicNetwork} provides a network transport based

on your choice of the Apache HTTP client {@code android.net.http.AndroidHttpClient} or

{@link java.net.HttpURLConnection}.</p>

on your preferred HTTP client.</p>

<p>{@code BasicNetwork} is Volley's default network implementation. A {@code BasicNetwork}

must be initialized with the HTTP client your app is using to connect to the network.

Typically this is a {@link java.net.HttpURLConnection}:</p>

<ul>

<li>Use {@code android.net.http.AndroidHttpClient} for apps targeting Android API levels

lower than API Level 9 (Gingerbread). Prior to Gingerbread, {@link java.net.HttpURLConnection}

was unreliable. For more discussion of this topic, see

<a href="http://android-developers.blogspot.com/2011/09/androids-http-clients.html">

Android's HTTP Clients</a>. </li>

<li>Use {@link java.net.HttpURLConnection} for apps targeting Android API Level 9

(Gingerbread) and higher.</li>

</ul>

<p>To create an app that runs on all versions of Android, you can check the version of

Android the device is running and choose the appropriate HTTP client, for example:</p>

<pre>

HttpStack stack;

...

// If the device is running a version >= Gingerbread...

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.GINGERBREAD) {

    // ...use HttpURLConnection for stack.

} else {

    // ...use AndroidHttpClient for stack.

}

Network network = new BasicNetwork(stack);

</pre>

Typically this is an {@link java.net.HttpURLConnection}.</p>

<p>This snippet shows you the steps involved in setting up a

{@code RequestQueue}:</p>

// Start the queue

mRequestQueue.start();

String url ="http://www.myurl.com";

String url ="http://www.example.com";

// Formulate the request and handle the response.

StringRequest stringRequest = new StringRequest(Request.Method.GET, url,

// Add the request to the RequestQueue.

mRequestQueue.add(stringRequest);

...

// ...

</pre>

<p>If you just need to make a one-time request and don't want to leave the thread pool

// Get a RequestQueue

RequestQueue queue = MySingleton.getInstance(this.getApplicationContext()).

    getRequestQueue();

...

// ...

// Add a request (in this example, called stringRequest) to your RequestQueue.

MySingleton.getInstance(this).addToRequestQueue(stringRequest);