Topic: Cache questions
We recently purchased Image & Filemanager, and it is functioning quite well.
I'm about to finish incorporating tinyMCE3 and the Image & Filemanager into our CMS. However I'm a little puzzled on finding a means to avoid the browser cache when desired.
Of course the browser should cache as much as possible for performance reasons, I utilize the tinymce_gzip.php?version=xxx variant to get this done properly.
This way, when upgrading to a new tinyMCE version the changed version param in the query string will trigger the clients browser to download the new JS code.
But what if the new version contains changes to .html / image files? These might still be cached by said browser.
Is it up to me to never let those files get cached? That's doable, but would hurt performance.
This also applies to Imagemanager & Filemanager.
Furthermore, if in Imagemanager an image is edited (i.e. cropped), and saved with the same filename it will remain cached as well. Thus no difference will be seen in advimg, or in the editor.
Could avoid this by not letting those images get cached at all, but maybe the Image manager could force (or default to) saving the image to a new filename? Then there would not a be cache problem.