> Isn't that an overkill ? create a service to share a single cursor > between 2 activities ? if it were a generic service that i used to > share many cursor from many queries (lets say it's a query management > service) and several activities will use it then i can understand the > efficiency and code simplicity in it, for more simple examples it > sounds like an overkill.
The other options you cited are bad for performance (putting the Cursor in an Intent extra) or are risky from a garbage collection standpoint (using mutable static data members). -- Mark Murphy (a Commons Guy) http://commonsware.com Android App Developer Books: http://commonsware.com/books.html -- 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en To unsubscribe, reply using "remove me" as the subject.
