> So now, if "rememberMe" is set to true, they don't need to enter their > username/passwrod anymore. Is this really the best way to go? Or > should I have made a UserBean and do that Java stuff, or should I have > stored that stuff in the SQLLite?
If you already have a database and wanted to keep everything in the same spot, setting up some sort of settings table there might make sense. Otherwise, your use seems tailor-made for simple preferences. > Alternatively, if I have rather few data to store, why not just use > SharedPreferences only and scrap the whole idea of using SQLLite? SQLite has more flexible query paths. Preferences are just key-value pairs. So, if you have 100 pieces of data and need to find a subset that meets some criteria other than keys, you're probably better suited with SQLite than stuffing those into preferences and having to sift through all of them on each "query". > Is there any built in encryption for any of these? Not that I'm aware of. I think the Bouncy Castle crypto package is included in the SDK, so you could encrypt values that you feel need full-fledged encryption. For passwords, you might be able to get by with just storing a hash of the password plus a salt. -- Mark Murphy (a Commons Guy) http://commonsware.com _The Busy Coder's Guide to Android Development_ -- Available Now! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
