Skip to content
This repository has been archived by the owner on Mar 14, 2021. It is now read-only.

Cache #33

Closed
scott-davidjones opened this issue Apr 7, 2014 · 4 comments
Closed

Cache #33

scott-davidjones opened this issue Apr 7, 2014 · 4 comments

Comments

@scott-davidjones
Copy link

Would it be possible to implement some cache functionality?

@raicabogdan
Copy link

product prices change hourly, so you can't really do that that.

@scott-davidjones
Copy link
Author

Hi,

I get that, but i keep getting throttle exceptions when trying to loop though each page of the search results..

edit

ok it seems as though the throttle is happening if i refresh the page to quickly..

@napolux
Copy link
Contributor

napolux commented Apr 7, 2014

You should really implement caching inside your app. Save the
price/status/whatever somehow and set a timer. If the object is older than
the timer, download it again, otherwise, use the cached one.

2014-04-07 17:01 GMT+02:00 Scott-David Jones notifications@github.com:

Hi,

I get that, but i keep getting throttle exceptions when trying to loop
though each page of the search results..

Reply to this email directly or view it on GitHubhttps://github.com//issues/33#issuecomment-39741135
.

Francesco Napoletano / Napolux
http://www.napolux.com

@scott-davidjones
Copy link
Author

ok sounds like a plan - thanks

this is a fantastic lib, saved me huge amounts of time. thanks

@Exeu Exeu closed this as completed Sep 29, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants