Ken
Sun Feb 01 20:44:05 CST 2004
You would allow the user to cache the page, and set an appropriate expiry
date/time (the date/time should be just before the page is rebuilt). The
browser will cache the page, and re-use it until the page has expired. Then
it'll go and get the new version.
Cheers
Ken
"Carroll P. MacDonald" <!0000@!00.000> wrote in message
news:%239svIWR6DHA.1672@TK2MSFTNGP12.phx.gbl...
: If it updates even once a day I don't think you will want to Cache it at
: all. If you Cache it you may find that people around the world will not
get
: the updated page unless they dump their Cache or Refresh that page, if you
: do not let the pages Cache they (the browser) will always check for a
newer
: version of that page.
:
: --
:
:
: Have a good one,
:
: Carroll P. MacDonald
:
http://www.pegusisfreeware.com/
:
:
:
:
:
: "A. Benz" <anonymous@discussions.microsoft.com> wrote in message
: news:D3A25F16-A1FA-4AC1-9506-DA2190F4F287@microsoft.com...
: > Hi,
: > I come from a unix background of web services and now I'm working with
an
: IIS box. The site that is being administered is compiled of ASP pages
with
: COM components on another server. A web user navigates to the index.asp
: page. This page is compiled and then creates an HTML string that is sent
to
: the web user's browser. I want to know where is that HTML string stored.
: In Memory, or on the server in a location.
: > in unix, it would be stored in the DOCROOT.
: > The reason I ask is because I want to be able to cache many pages on my
: site. Since most pages are updated only twice daily, there is no need to
: process the ASP page every single time a web user navigates to that page.
: >
: > Can anyone help me
: > thanks
: >
:
: