Viewing 1 replies (of 1 total)
  • Plugin Author Spencer Cameron-Morin

    (@spencercameron)

    Codespanker Cache works great with a CDN. Since it caches the page content itself, images and other assets would still need to be served. A CDN would be a great compliment in this case.

    The plugin currently supports full-page caching. That means once your server generates a page ( when the page is visited and there isn’t currently a cached copy ), subsequent visitors are served the cached copy until the cached copy expires. It’s hard to say whether or not this would interfere with caching you already have set up.

    Can you explain what server-side caching is already being done?

Viewing 1 replies (of 1 total)
  • The topic ‘I'm already on a CDN, should I deploy CSpanker?’ is closed to new replies.