On Mon, Mar 19, 2012 at 11:40 AM, RedBullet <[email protected]>wrote:
> I am wondering if it makes sense to contain all that state/logic in the > service, or if I should put as much of the common state into an Application > class, and let the activities/services access it through the application > class. Well, now you're getting into architecture questions for your business-specific logic, so that's really ultimately up to you. Personally, I would abstract that logic into its own class(es), which are then accessed from wherever they're needed, whether it be the background service the current foreground activity. As Singletons, perhaps? ------------------------------------------------------------------------------------------------- TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago transit tracking app for Android-powered devices -- 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
