Thursday, July 29, 2010

Re: [android-developers] Re: bindService() does not create local service, but returns true

Not all services are local.

I guess that's the main reason for async protocol, which assumes the most general case. But then again, only developers of Android know for sure :-)

--
Kostya Vasilyev -- http://kmansoft.wordpress.com

30.07.2010 1:01 пользователь "Jeroen Kransen" <jeroen@kransen.nl> написал:

Thank you so much, Kostya! Indeed it turns out to be an asynchronous
call. It makes the design of the Activity slightly more verbose, but
at least I got it working. Are there imperative reasons why the
service is not returned synchronously? Is it very costly to
(instantiate and) return a local Service? If not, it would be a nice
feature to have the bindService block, or at least to have the option
through a method parameter that we want to wait for it like
bindService(..., boolean willWait).

Thanks again!

Jeroen


On 29 jul, 22:32, Kostya Vasilyev <kmans...@gmail.com> wrote:
> If I remember right, starting a ser...

> 30.07.2010 0:21 пользователь "Jeroen Kransen" <jer...@kransen.nl> написал:

>
> This is the only serious logging I get in LogCat. Sometimes after that
> I get a timeout on the ...

--
You received this message because you are subscribed to the Google
Groups "Android Developers" g...

--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

No comments:

Post a Comment