what is the best practices to keep data between activities deathes/restarts for the whole application session?

by Arhimed » Sat, 09 Jan 2010 03:27:44 GMT


Sponsored Links
 We're designing an app that has several activities which are working
in a wizard like way - user should pass from the activity #1 to
activity #5 to get to the final activity (#6).

Since we know an activity can be suddenly terminated by OS on low
memory we used Application class as a static storage for keeping the
data the user inputs on "wizard" activities and other data our app
needs for the whole session.

Unfortunately we've discovered this approach fails - looks like the
Application class instance is also can be killed by OS (this was
specifically discovered on Android 1.6 versus 1.5). Are our
expectations wrong on this approach (we think Application class
instance always lives for the whole app session)?

So the question is - what is the best practices to keep data between
activities deathes/restarts for the whole application session?



Other Threads

1. Aplikasi google baru nih

meluncur ke tkp lewat push appbrain ah sekalian nyoba fast web installer :)

2010/7/10 lucky sebastian <9b.andr...@gmail.com>

> 

2. Android Kernel Vs Linux Kernel.

> Is there anything that is specific to android in kernel level. (i.e)any

Yes.


You already found them.


You already have all of the diffs on what is needed to do.


Look at the changes relative to the "stock" kernel.org release and you
will see the android specific changes.

good luck,

greg k-h

-- 
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: 

3. FM Radio on N1, a light at the end of the tunne

4. ada yang punya apk MidpPlayer

5. iAd, a revolution

6. How to manage an event by 2 widgets

7. Is there any possibility for read and write to sdcard in ndk layer?