Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a ContentProvider #88

Closed
przybylski opened this issue Aug 30, 2013 · 1 comment
Closed

Create a ContentProvider #88

przybylski opened this issue Aug 30, 2013 · 1 comment

Comments

@przybylski
Copy link
Contributor

And implement this backend as Provider, this way it can be more consistent with platform and easly extendable.

(original title:Move cache backend to database instead of filesystem)

@mauimauer
Copy link
Member

Hmmm...not sure about that. I'd say using SQLite for our kind of application is overkill. Additionally we rely on several non standardized data sources that could change at any time. I'd rather fixup a POJO than managing/migrating SQL tables. Having a content provider is nice an might be something for the roadmap. But it's certainly no pressing issue.

@friedger friedger closed this as completed Nov 9, 2013
@friedger friedger reopened this Nov 9, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants