ok, thanks!
On Apr 2, 11:24 pm, "Joe Onorato" <[EMAIL PROTECTED]> wrote:
> Hi Anil,
>
> This is not correct. Here are a few examples: If your app has two
> services, there will be two different contexts running at the same time. If
> your app has two activities, one will still have methods run
Hi Anil,
This is not correct. Here are a few examples: If your app has two
services, there will be two different contexts running at the same time. If
your app has two activities, one will still have methods running after
onPause. Messages sent may be handled while another activity is still
ru
Again, please correct me:
But unlike J2SE, here in Android, zero or one contexts are 'active' or
relevant in a thread.
The thread started life and meandered along touching different
contexts along the way.
In other words, it is possible to state which was the last context
touched, and will be rele
On Apr 1, 3:35 pm, trickybit <[EMAIL PROTECTED]> wrote:
> Isn't it the case that these calls are run on threads belonging to the
> called process, but these are not the main thread, and they model a
> synchronous call on the calling thread?
True for most of the calls on ContentProvider (content p
On Mar 31, 9:25 am, hackbod <[EMAIL PROTECTED]> wrote:
> Also, calls to service interfaces and content providers
> are executed in the calling thread, not their own thread.
Isn't it the case that these calls are run on threads belonging to the
called process, but these are not the main thread,
That is not true, all of the activities (and intent receivers and
services) are called in the main thread of the process they are
running in. Also, calls to service interfaces and content providers
are executed in the calling thread, not their own thread.
On Mar 31, 8:51 am, Anil <[EMAIL PROTECT
6 matches
Mail list logo
