Image updating very, very slow

Lindsi Gish

I don't know if it's just me, but no matter if I'm using the Image Library or FTPing an image to our Convio site, it seems it's always incredibly slow to replace an existing image. It shows up automatically if I name it something new, but if "imagex.jpg" exists, I should be able to replace "imagex.jpg" and have it reflect right away on our PageBuilder page. It's not a browser thing - I clear the cache, do hard refreshes and switch browsers - and it's always the same story. In addition, replacing an image in the Image Library with another image never seems to work. Or maybe it does work, but it takes so long to update on the page that I can't really tell.

Do other clients have this problem? Is there anyone from Convio who can speak to why this happens?

I  have never had this problem with another host, so it's pretty irritating.

Michael

Convio does server-side caching for performance reasons, so any image (or javascript or CSS file) that you change after it's been cached on the server will not show the new version until the cache is refreshed.  I'm not sure of the actual TTL (time to live) setting for the cache, but I think it's around 15 minutes.  You can't make that happen manually.  It's incredibly frustating when you're trying to tweak something to be sure.  I actually wrote my own Greasemonkey script in FireFox to work around this issue...

It's annoying to develope with this, but it's a *good* thing for performance reasons.  It greatly reduces load across the board and, really, you can't call any environment "high availablity" if it's not doing some sort of server-side caching.

Long story short (now that you read the long story.....):  It's by design. 

Lindsi Gish

Michael :

Convio does server-side caching for performance reasons, so any image (or javascript or CSS file) that you change after it's been cached on the server will not show the new version until the cache is refreshed.  I'm not sure of the actual TTL (time to live) setting for the cache, but I think it's around 15 minutes.  You can't make that happen manually.  It's incredibly frustating when you're trying to tweak something to be sure.  I actually wrote my own Greasemonkey script in FireFox to work around this issue...

It's annoying to develope with this, but it's a *good* thing for performance reasons.  It greatly reduces load across the board and, really, you can't call any environment "high availablity" if it's not doing some sort of server-side caching.

Long story short (now that you read the long story.....):  It's by design. 

Bummer, but at least now I know. Thanks!