Jordan Cook
Jordan Cook
Hi @tomasbasham, first of all thanks for this handy package. It solves a small but common enough problem such that this is currently the top Google result for "python rate...
Not 100% sure yet about how `Cache-Control: must-revalidate` is supposed to behave, but I'm currently interpreting it to mean "don't serve a stale cached response if some other header/setting would...
DynamoDB has a fairly small max item size (400KB). For typical web scraper/API client use cases, this is sufficient. For larger responses, though, it would be very useful to be...
Currently, the filesystem backend stores all response files in a single directory. This is for convenience in the main use case it was intended for: being able to manually view/edit...
GridFS backend: store response metadata in regular MongoDB collection, and response body in GridFS
Related to #576. This would require adding a 3rd storage object for response content. So a total of 1 GridFS store, and 2 MongoDB collections: * `content` * `responses` *...
Currently, the filesystem backend uses a simple threading lock for thread safety. To be safe for multiple processes, it will need a file-level locking mechanism, like [py-filelock](https://py-filelock.readthedocs.io). That could be...
Related to #407. This would help with some use cases that have come up a few times now: * Efficiently storing large response contents (without the serialization bottleneck) * Caching...
I believe this is mainly useful for servers that want to ensure the cache can properly deal with 206 and 304 responses. 304s have been supported since 0.8. It will...
requests-cache has been around since 2012, but still has `0.x` version numbers. I think it would be reasonable to finally give this a major version bump to 1.0 sometime in...
Before the 1.0 release, the user guide docs need another thorough review to make sure everything is up to date and accurate.