On Sep 28, 2:09 pm, Mark Murphy wrote:
> GeezIHateCreatingNewNames wrote:
> > The more complicated case
> > seems to be a single application that has two processes in it (e.g, an
> > application with a long running service).
>
> You do not need two processes for an application with a long runnin
GeezIHateCreatingNewNames wrote:
> The more complicated case
> seems to be a single application that has two processes in it (e.g, an
> application with a long running service).
You do not need two processes for an application with a long running
service. Not to mention that long-running service
I've also struggled with the the distinction between a ContentProvider
and just using a sqlite database. Clearly if the application is
exporting data to other (potentially unknown) applications then a
ContentProvider would make some sense. The more complicated case
seems to be a single applicati
If you need the features content provider adds (primarily interaction across
separate application and associated discovery and cross-process calls, as
well as MIME typing to integrate with intent resolution) then consider using
it. Otherwise there probably isn't a reason to.
On Thu, Sep 10, 2009
Hi Dianne,
i get ur point that Content provider is built on top of SQlite but i
wanna know is what additional features does a provider support. Say if
a make my own Database Store class and provide methods in it to
insert/update/delete into a database.
And if i create a Provider for the same
Content provider is (generally) built on top of SQLite. You don't pick one
or the other.
On Wed, Sep 9, 2009 at 9:24 PM, Chris wrote:
>
> I would like to know the exact difference between Content provider and
> SQLiteDatabase. If we have to share our data among applications then
> we use Conten
6 matches
Mail list logo
