L
Leo Muller
I am impressed by the caching performance of .NET. However, there is one
major obstacle that I haven't managed to solve yet.
What I want to do is the following: I have a normal site, and a preview
site. The normal site should have maximum performance, thus uses caching.
The preview site is for internal use only, and should not use caching, since
our content managers will want to see the updates directly. The only
difference between the two sites is the web.config file.
If I use caching programmatically, then everything works out great, I add a
key in the webconfig, and only if this is the normal site then it will do
caching, otherwise it won't.
But if I use the caching through the page directives, <@OutputCache
Duration="300" VaryByParam="none"%>, then I can't vary this anymore between
my preview site and my normal site.
How can I overcome this problem?
Leo Muller
major obstacle that I haven't managed to solve yet.
What I want to do is the following: I have a normal site, and a preview
site. The normal site should have maximum performance, thus uses caching.
The preview site is for internal use only, and should not use caching, since
our content managers will want to see the updates directly. The only
difference between the two sites is the web.config file.
If I use caching programmatically, then everything works out great, I add a
key in the webconfig, and only if this is the normal site then it will do
caching, otherwise it won't.
But if I use the caching through the page directives, <@OutputCache
Duration="300" VaryByParam="none"%>, then I can't vary this anymore between
my preview site and my normal site.
How can I overcome this problem?
Leo Muller