Thanks, using Application seems to be the best way, and in the event I need to store this on disk later, I can use a ContentProvider.
On Apr 9, 1:22 am, Ted Hopp <[EMAIL PROTECTED]> wrote: > If the data will only be accessed strictly within your application, > then extending Application is the easiest way to go. Otherwise the > Android way is to create a content provider. Storing transient data in > static variables is not reliable. > > On Apr 8, 3:15 pm, Soonil Nagarkar <[EMAIL PROTECTED]> wrote: > > > I am wondering, what is the best way to store somewhat transient data > > in a manner so that it is easily reachable across an entire > > application? In this case, it is a type of buddy list that is valid > > across a session. I would like any Activity, Service, etc... in my > > application to be able to read the same data. > > > There seem to be two possibilities, storing the information or storing > > on disk. Storing on disk offers the SQLite database or files as a > > backend, but this is a bit heavierweight than I want. I would prefer > > to store the information in memory. I cannot find any good advice as > > to what the best way to do this is however. > > > I have found some information about the Application class, which > > offers some of what I am looking for, but I am not sure if this is the > > best method, or the proper -Android way- to accomplish this. Any > > thoughts or advice? --~--~---------~--~----~------------~-------~--~----~ 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] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
