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

Caching sync call results? #12

Open
razzeee opened this issue Feb 6, 2015 · 3 comments
Open

Caching sync call results? #12

razzeee opened this issue Feb 6, 2015 · 3 comments
Labels

Comments

@razzeee
Copy link
Contributor

razzeee commented Feb 6, 2015

Should this be done in our apps? Might be nice to have this centrally, might also be overkill.
Would have to save timestamps to our sync/collection sync/watched calls and compare them with the result of last activity for that task http://docs.trakt.apiary.io/#reference/sync/last-activities/get-last-activity which we would call before doing anything else.

@fuzeman
Copy link
Owner

fuzeman commented Feb 7, 2015

I've been thinking about building a separate syncing library (e.g. trakt.sync.py), this could contain some common classes/tools like this.

I don't really have the time to work on this yet.. there are some higher priority issues to resolve in trakt/Plex-Trakt-Scrobbler before this.

@fuzeman fuzeman added the feature label Feb 7, 2015
@razzeee
Copy link
Contributor Author

razzeee commented Feb 7, 2015

Sounds nice. If I can help just let me know. My python is still weak.

@fuzeman fuzeman mentioned this issue Mar 12, 2015
@fuzeman
Copy link
Owner

fuzeman commented Mar 22, 2015

I've started implementing a sync cache (available in trakt.sync.py) and storage backend (stash).

Still needs a lot more testing, wouldn't use this in production yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants