Skip to main content

android device to backup data on local server



I am working on the android application that would perform functionality and ultimately save the data(Highly Confidential) in a local server, I am a newbie, I need ideas from you people in the shape of steps that i need to follow for the implementation. I cant expose the main main idea but the thing is store the customer data (in the database placed on server) on the server via android tablets, there will be multiple tablets feeding the data in parallel. I will appreciate if someone would suggest the appropriate tutorials (for webservice creation/usage etc)




Comments

  1. Follow this link written by Roto Meier, it very well explains how you should back up the data.

    The following is an excerpt from it..

    "The Backup Manager was added to Android in Froyo and it's about as trivial to implement as I can conceive.
    All you need to do is extend the BackupAgentHelper and create a new SharedPreferencesBackupHelper within it's onCreate handler.
    As shown in the PlacesBackupAgent, your Shared Preferences Backup Helper instance takes the name of your Shared Preference file, and you can specify the key for each of the preferences you want to backup. This should only be user specified preferences - it's poor practice to backup instance or state variables."

    public class PlacesBackupAgent extends BackupAgentHelper {
    @Override
    public void onCreate() {
    SharedPreferencesBackupHelper helper = new
    SharedPreferencesBackupHelper(this, PlacesConstants.SHARED_PREFERENCE_FILE);
    addHelper(PlacesConstants.SP_KEY_FOLLOW_LOCATION_CHANGES, helper);
    }
    }


    "To add your Backup Agent to your application you need to add an android:backupAgent attribute to the Application tag in your manifest."

    <application android:icon="@drawable/icon" android:label="@string/app_name"
    android:backupAgent="PlacesBackupAgent">


    "You also need to specify an API key (which you can obtain from here: http://code.google.com/android/backup/signup.html)"

    <meta-data android:name="com.google.android.backup.api_key"
    android:value="Your Key Goes Here" />


    "To trigger a backup you just tell the Backup Manager that the data being backed up has changed. I do this within the SharedPreferenceSaver classes, starting with the *FroyoSharedPreferenceSaver*."

    public void savePreferences(Editor editor, boolean backup) {
    editor.commit();
    backupManager.dataChanged();
    }

    ReplyDelete
  2. There is a ton of HTTP Based services frameworks, and almost every pure java framework
    (like CXF, Axis etc.) client will run on android - you just have to pick one that sucks less (this is hard part) and is easier to handle.

    For confidential and sensitive data I would use encrypted channels - but this is framework
    independent.

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex