You can call execute(...) once on one instance of an AsyncTask. But
you can create a new instance of an AsyncTask and call execute(...) on
that new instance.
Multiple instances of an AsyncTask share a limited pool of threads. An
AsyncTask instance is put into a queue when 'execute(...)' is called
I hope you realize that the service won't actually start until *after*
the method on the main thread that started it exits. This is true even
if you start up another thread to start the service. Starting the
service -- even an IntentService -- requires that the main thread be
free. (It's somewhat
2 matches
Mail list logo
