.. but on the other hand I can't handle results from different activities as I could do firing a broadcast message from the service....
On 10 Nov, 23:03, Kostya Vasilyev <[email protected]> wrote: > Yes, ResultReceiver seems really nice - it's more lightweight than a > broadcast intent, and requires less "wiring" both in the manifest and in the > code. > > -- > Kostya Vasilyev --http://kmansoft.wordpress.com > > 11.11.2010 0:49 пользователь "Federico Paolinelli" <[email protected]> > написал: > > I was looking to existing source code to get some inspiration, and I > came across the google io 2010 schedule app. > > They still use an intent service to perform the calls, but they use > another way to fetch the result of the webservice interaction, which > is sending to the intent service a parceled ResultReceiver to be > called to be notified of the result. > > I am not sure that this approach is better compared to returning the > result bundled in a broadcast (any ideas?), but in any case I think I > will go with the intent service in order to save some resources. > > Federico > > On Wed, Nov 10, 2010 at 8:12 AM, Federico Paolinelli <[email protected]> > wrote:> On 10 Nov, 00:58... > > -- > -------- > > Federico > > -- > You received this message because you are subscribed to the Google > Groups "Android Dev... -- 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
