We can maintain cache/history of our visited entries in our mobile.
The method that can be used is "RecordStore"
how to do it:
1) Open a recordstore
2) add records to it.
Note: They'll be stored into mobile memories, you can't see these records as such in mobile
Now, when you want to view these records, open the recordstore again if it's closed. just open each record and perform the function.
You can append these records in a list so as to show them as a history maintained.
Problem welcome...
The method that can be used is "RecordStore"
how to do it:
1) Open a recordstore
2) add records to it.
Note: They'll be stored into mobile memories, you can't see these records as such in mobile
Now, when you want to view these records, open the recordstore again if it's closed. just open each record and perform the function.
You can append these records in a list so as to show them as a history maintained.
Problem welcome...
Hi, My team has come up with a very simple mobile app for devices having java or symbian o/s. The challenge is we need to store data in the LDS of the handsets since the users of such app may not be always connected to internet, its a GPRS app. We wish to know how to implement cache to store small data in the handsets. And how do we identify what data to store. you may mail me karabi.bharadwaj@gmail.com, thanks.
ReplyDeleteWhat I pre-assume that your mobile is java enabled and you are using J2ME to develop that app.
ReplyDeleteNow, coming to your question
1) how to implement cache to store small data in the handsets?
There is already provision in J2ME for caching mechanism. The API that implements it is *RecordStore*. Basically whatever records/data you want to cache is stored in mobile's internal memory. It's not accessible to you. Once you run the app again then only you can view the cached contents.
So, you can write a function to be called each time you enter some value inside your app, which can open the already existing cache data (known as record store in J2ME) and write it to your new record/data.
2) how do we identify what data to store?
It depends on your app what you want to actually cache. The most frequently used data is generally cached. So, it totally depends upon your requirement. e.g., I used to send messages to only 4 of my friends out of my 1000 contacts. Then ofcourse, I would like to use their contacts as frequently as possible instead of typing or searching the contact details again and again.