Ah, sorry, I missed that. On Wed, Dec 22, 2010 at 2:58 PM, Kostya Vasilyev <[email protected]> wrote: > 22.12.2010 22:15, Mark Murphy пишет: >> >> activity run on the main application >> thread (which you are blocking) > > Mark, > > I don't believe this is the case. > > In fact, Schoel wrote this in his original message: > >> I've checked the thread id of the thread in which queryUserSave is >> called and the thread id in which the QueryUserSaveActivity is started >> (if I don't use any semaphores) and they are not the same. > > Since activity always run on the UI thread, the above implies that the > original entry point into the code, queryUserSave, is called on a background > thread. > > A background thread, unlike the UI thread, can be blocked as necessary, > using wait() or other means, until it's time for it continue. > > -- Kostya > > -- > Kostya Vasilyev -- WiFi Manager + pretty widget -- > http://kmansoft.wordpress.com > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en >
-- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to *Advanced* Android Development_ Version 1.9 Available! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
