We have a multi-activity app that needs to communicate with a remote service with a callback interface. Each activity needs to access the remote service and receive callback messages from it (either directly or indirectly). What are some good practices for designing this? Here are some options:
- store the reference to the service reference in the global Application Context and have it implement the callback interface (don't know if this is possible) - have each activity implement the callback interface and communicate with the service using its own IPC channel - Have 1 activity own the service reference and implements the callback interface (thus serving as hub for all IPC activity). We do run into a problem that this activity's lifetime may be shorter than the foreground activity that depends on it to send RPC messages. -- 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
