Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>You have four realistic solutions i would say in my opinion</p> <p><strong>1-</strong> Threads</p> <p><strong>2-</strong> Asyntask</p> <p><strong>3-</strong> Service</p> <p><strong>4-</strong> External lib</p> <p>If you are doing lot of small downloads classic <strong>Theading</strong> is the best option maybe with a service to manage it, but not forced.</p> <p>For one simple download you can use <strong>Asynctask</strong> alone. It can be enough but you must know several things about this method : AsyncTask can be "Bugged" according to the way you use it.</p> <p><strong>Service</strong> is good you can use it. A download module using service is a good idea to manage the requests.</p> <p>The best solution for a quick/efficient developement is to use a library that do the work for you. But in your case you are using SOAP... If you where using Json you could make use of <strong>Volley</strong> which is very good and fast.</p> <p>Maybe try to use this one which is well known </p> <p><strong><a href="http://code.google.com/p/ksoap2-android/" rel="nofollow">http://code.google.com/p/ksoap2-android/</a></strong> </p> <p>with the how to <strong><a href="http://code.google.com/p/ksoap2-android/wiki/HowToUse" rel="nofollow">http://code.google.com/p/ksoap2-android/wiki/HowToUse</a></strong></p> <hr> <p>For the moment when to do the operation you have several solutions</p> <p><strong>1-</strong> In background without blocking the ui, updating the ui View per View</p> <p><strong>2-</strong> Using a loading screen (bad for user experience but sometimes you don't have a choice)</p> <p>In your case you would have the loading screen between the first activity and the second using a ProgressDialog maybe</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload