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

Use SS_Cache to cache expensive API calls #1

Open
madmatt opened this issue Jul 15, 2014 · 0 comments
Open

Use SS_Cache to cache expensive API calls #1

madmatt opened this issue Jul 15, 2014 · 0 comments

Comments

@madmatt
Copy link
Owner

madmatt commented Jul 15, 2014

Caching needs to be carefully thought through, given we're connecting to an external API, this may be slow to access, but we need to ensure we're as up to date as possible, given the external API could change at any time (users are expected to be using both the FreshBooks interface as well as these classes to modify their FreshBooks account, so data could change at any time).

Some potential low-hanging fruit for caching (perhaps an hour cache lifetime?):
* category.list, category.get (any other category.* method should invalidate or update the cache)
* client.list, client.get (any other client.* method should invalidate or update the cache)
* estimate.list, estimate.get (any other estimate.* method should invalidate or update the cache)

Same goes for all the other get/list methods, they're pretty similar. Cache lifetimes will need to be carefully decided.

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

No branches or pull requests

1 participant