A ContentProvider doesn't have to be SQL based - you can store the data
in memory, as long as you use a Cursor subclass that's not SQL based either.
What is a "very long" String?
Depending on your data size, you may want to use Messenger:
http://developer.android.com/reference/android/os/Messenger.html
-- Kostya
15.07.2011 14:38, sriram пишет:
Hi ,
I have a scenario where data needs to be continously exchanged between
two applications or rather, one application acts as the data provider
and the other simply uses it.
I am thinking of two possible solutions,
1. Use the sendBroadcast() - broadcast a app-directed intent with the
specific data
2. Make the data provider application as a content provider, where all
the data is written to sqlite data base, and the first application
queries for the data after every x seconds.
Here the data is mostly String, but can be a very long String.
The frequency of updates is very frequent.
The two applications cannot be combined.. :(
I am not sure of the implications of either approach, fast vs
performance vs preferred..
What should be the suggested approach?
Thanks in advance..
--
Kostya Vasilyev
--
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]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
