On 27 Ago, 23:58, Maps.Huge.Info (Maps API Guru) cor...@gmail.com
wrote:
I think the consensus is that AsyncTask is the way to go if what
you're trying to do affects the UI thread eventually. Using a service
to compute location for instance would be over complicated.
-John Coryat
Maybe I
I suppose you'd be better off with a service per service instead of
one god service. The reason is that it make the code cleaner - you
don't need to manage multiple alarms and network connections in one
class. An exception would be a service that just does one kind of
thing, but handles a queue of
On 28 Ago, 18:32, Frank Weiss fewe...@gmail.com wrote:
I suppose you'd be better off with a service per service instead of
one god service. The reason is that it make the code cleaner - you
don't need to manage multiple alarms and network connections in one
class. An exception would be a
I'm not a total expert on this...
Threads are really just a way of running multiple stacks/program
counters in the same address space. It's fair to assume they are
time-sliced. Services and Activities are run in a single UI thread
(AFAIK) and the precessing model is typical UI thread which calls
On Sat, Aug 28, 2010 at 7:25 PM, Frank Weiss fewe...@gmail.com wrote:
I'm not a total expert on this...
Threads are really just a way of running multiple stacks/program
counters in the same address space. It's fair to assume they are
time-sliced. Services and Activities are run in a single UI
I think the consensus is that AsyncTask is the way to go if what
you're trying to do affects the UI thread eventually. Using a service
to compute location for instance would be over complicated.
-John Coryat
--
You received this message because you are subscribed to the Google
Groups Android
6 matches
Mail list logo
