railgunner

Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter railgunner

    (@railgunner)

    Thanks for your answer, Destac.

    But I’m assumming that time is the expiration set in the headers for the browser to keep CSS in cache, right? I’m wondering if there is a value elsewhere that states when Total Cache will discard existing minified CSS files and calculate them again.

    Hi. First of all, Nevma, thank you for your efforts and please excuse my delay… could not try it on some test web until now…

    I’m using Adaptive Images 0.6.2, so far looks promising. But I have some question, could you please elaborate on the meaning of the GET parameter?

    1) I see the plugin is serving XXX?resolution=1024,1 1024 looks OK but, what is the “,1”? Pixel density?
    2) I can also see XXX?resolution=1920,1 and ?resolution=667,2 I have no “1920” entry in Adaptive settings, and 667 doesn’t seem to make sense either. And why the “,2”?

    I understand that this is for CDN only, and the image is served as needed based on device’s resolution and ignoring the extra params… Is that true or does Adaptive indeed try to serve “?resolution=667,2”?

    By the way: 1280, 1024, 640 and 360 subdirs have been created in the cache directory, as expected.

    Thanks and regards!

    One could add a url parameter at the images via Javascript… I will sleep on it.

    That would be great! Thank you for your efforts.

    Hi:

    First of all, congrats on the plugin. Really useful.

    I would also be interested in some form of CDN compatibility. How about a configuration option to serve scaled images with diferent URLs depending on the resolution? If this could be implemented, though not the perfect solution, it would force the CDN to cache diferent versions of the image as needed.

    Regards.

Viewing 4 replies - 1 through 4 (of 4 total)