«

We are about to move our web site to be more dynamic - people will be
editing things like text strings on a page. This stuff won't change very
often. I was wondering if Output Caching would be reasonable so that the
pages don't get regenerated every time somebody goes to a page.

Would Output Caching be appropriate here? What's a reasonable duration to
keep the page cached? I assume that memory becomes an issue as you cache
more and more stuff. How does the system know whether to use the cached page
or not? For instance - I log in as user X - on the page it says User X
(which I got from the code behind.) User Y logs in. I assume it will not
use the cached page because it 'knows' it's different. Is that true?

TIA - Jeff.

Jeff,
The only problem with caching is that not enough developers have taken the
time to become smart enough to use it!


Here's an article that attempts to pull a lot of useful information into one
place:

http://www.eggheadcafe.com/articles/20060407.asp

Peter


--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com




"UJ" wrote:

> We are about to move our web site to be more dynamic - people will be
> editing things like text strings on a page. This stuff won't change very
> often. I was wondering if Output Caching would be reasonable so that the
> pages don't get regenerated every time somebody goes to a page.
>
> Would Output Caching be appropriate here? What's a reasonable duration to
> keep the page cached? I assume that memory becomes an issue as you cache
> more and more stuff. How does the system know whether to use the cached page
> or not? For instance - I log in as user X - on the page it says User X
> (which I got from the code behind.) User Y logs in. I assume it will not
> use the cached page because it 'knows' it's different. Is that true?
>
> TIA - Jeff.
>
>
>

Cool Peter. Thanks for the info.

Jeff.

"Peter Bromberg [C# MVP]" <> wrote in message
news:B651DB77-6E61-4A8F-B531-...
> Jeff,
> The only problem with caching is that not enough developers have taken the
> time to become smart enough to use it!
>
>
> Here's an article that attempts to pull a lot of useful information into
> one
> place:
>
> http://www.eggheadcafe.com/articles/20060407.asp
>
> Peter
>
>
> --
> Co-founder, Eggheadcafe.com developer portal:
> http://www.eggheadcafe.com
> UnBlog:
> http://petesbloggerama.blogspot.com
>
>
>
>
> "UJ" wrote:
>
>> We are about to move our web site to be more dynamic - people will be
>> editing things like text strings on a page. This stuff won't change very
>> often. I was wondering if Output Caching would be reasonable so that the
>> pages don't get regenerated every time somebody goes to a page.
>>
>> Would Output Caching be appropriate here? What's a reasonable duration to
>> keep the page cached? I assume that memory becomes an issue as you cache
>> more and more stuff. How does the system know whether to use the cached
>> page
>> or not? For instance - I log in as user X - on the page it says User X
>> (which I got from the code behind.) User Y logs in. I assume it will not
>> use the cached page because it 'knows' it's different. Is that true?
>>
>> TIA - Jeff.
>>
>>
>>