By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,581 Members | 1,990 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,581 IT Pros & Developers. It's quick & easy.

Best output cache practices?

P: n/a
Hi,
We have IIS 6.0 servers and we want to take advatage of the kernel-mode
caching feature by using output cache directive in certain pages.
As far as I understand, IIS saves for each (unique) request the appropriate
response...

When the page is first loaded, followed by GET request, there is one
response for all users.
But the problems starts when the user submits the form (POST) -
the response could not be a static cached page, because expiration of data
and different responses for different users.
So playing with the submit button caused problems...

Another thing is memory usage - there is only one GET request but many POST
requests...(Important?)

Is there anything else to consider when output caching?
How can you cache only the GET requests?

Thanks in advance,
Hadar.

Nov 19 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
Hi Hadar:

Eon has some tips:
http://geekswithblogs.net/ewright/ar...10/24/241.aspx

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Mon, 21 Mar 2005 13:08:03 +0200, "Hadar" <cr****@bezeqint.net>
wrote:
Hi,
We have IIS 6.0 servers and we want to take advatage of the kernel-mode
caching feature by using output cache directive in certain pages.
As far as I understand, IIS saves for each (unique) request the appropriate
response...

When the page is first loaded, followed by GET request, there is one
response for all users.
But the problems starts when the user submits the form (POST) -
the response could not be a static cached page, because expiration of data
and different responses for different users.
So playing with the submit button caused problems...

Another thing is memory usage - there is only one GET request but many POST
requests...(Important?)

Is there anything else to consider when output caching?
How can you cache only the GET requests?

Thanks in advance,
Hadar.


Nov 19 '05 #2

P: n/a
Hi Scott,
Thanks you, it looks like it's working great!
Hadar

"Scott Allen" <sc***@nospam.odetocode.com> wrote in message
news:pd********************************@4ax.com...
Hi Hadar:

Eon has some tips:
http://geekswithblogs.net/ewright/ar...10/24/241.aspx

--
Scott
http://www.OdeToCode.com/blogs/scott/

On Mon, 21 Mar 2005 13:08:03 +0200, "Hadar" <cr****@bezeqint.net>
wrote:
Hi,
We have IIS 6.0 servers and we want to take advatage of the kernel-mode
caching feature by using output cache directive in certain pages.
As far as I understand, IIS saves for each (unique) request the appropriateresponse...

When the page is first loaded, followed by GET request, there is one
response for all users.
But the problems starts when the user submits the form (POST) -
the response could not be a static cached page, because expiration of dataand different responses for different users.
So playing with the submit button caused problems...

Another thing is memory usage - there is only one GET request but many POSTrequests...(Important?)

Is there anything else to consider when output caching?
How can you cache only the GET requests?

Thanks in advance,
Hadar.

Nov 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.