Open youknowone opened 9 years ago
Does it purpose to invalidate client-side caching?
Yes. It seems there are cases not able to invalidate them with query strings.
Is the problem caused by query string, or impossibility to determine when exactly things are updated?
Impossible to determine image is changed. The cache service is checking only the filenames.
Okay. So there a trivial suggestion: passing an actual datetime
value would be better than its encoded string representation, namely created_id
. I think the better place of responsibility for how the created time has to be encoded is Store
rather than Image
. It gives more flexibility for supporting various store backends (for example, it can be used for providing Last-Modified
header). What’s your opinion about this?
Fixed
Getting unique path for image changing is useful, but missing feature (though it is able to be implemented in user side)
This patch includes breaking changes:
created_id
argument to each put, get, delete methodscreated_id
argument