I see there is a CachingTimeSpan setting in the config to apply client side caching. I appreciate how more useful this can be when dealing with different classes. However, this isn't required on a current project and I would instead like to keep all my client side caching within IIS itself. All caching in one place, and less fiddling with files when deploying to different servers. Is this possible?
I don't think so because ImageGen Basic always sets the headers to include an ETag and the cache time to zero. You could perhaps figure a way to remove the headers from ImageGen and have IIS set them again I suppose.
This is an unintended consequence of ImageGen Basic - the goal is to always ask the server if a new version of the image has been put on the server. With the ETag and other caching information ImageGen can respond with either a new image to your specifications or simply give a tiny and quick 304 response. This is all server-side caching.
ImageGen Professional lets you add client-side caching. It's all configured in the imagegen.config file and can be set on a per-class basis or in the 'default' class if you want every request to be cached some minimum amount.
Thanks for the quick reply Doug. I suppose another HTTP Handler to override ImageGen cache settings would work. It looks like we'll probably have to upgrade though if the client can agree the cost. Hopefully we can convince them the £125 is worth it for the performance boost and server load.
Use IIS For Client Side Caching
Hi,
I see there is a CachingTimeSpan setting in the config to apply client side caching. I appreciate how more useful this can be when dealing with different classes. However, this isn't required on a current project and I would instead like to keep all my client side caching within IIS itself. All caching in one place, and less fiddling with files when deploying to different servers. Is this possible?
Thanks,
Duncan
I don't think so because ImageGen Basic always sets the headers to include an ETag and the cache time to zero. You could perhaps figure a way to remove the headers from ImageGen and have IIS set them again I suppose.
This is an unintended consequence of ImageGen Basic - the goal is to always ask the server if a new version of the image has been put on the server. With the ETag and other caching information ImageGen can respond with either a new image to your specifications or simply give a tiny and quick 304 response. This is all server-side caching.
ImageGen Professional lets you add client-side caching. It's all configured in the imagegen.config file and can be set on a per-class basis or in the 'default' class if you want every request to be cached some minimum amount.
cheers,
doug.
Thanks for the quick reply Doug. I suppose another HTTP Handler to override ImageGen cache settings would work. It looks like we'll probably have to upgrade though if the client can agree the cost. Hopefully we can convince them the £125 is worth it for the performance boost and server load.
is working on a reply...