RE: meta tag

Not sure if this would help you, but here's the approach I use for our
company's web-based document control system:

Whenever I make changes to the documentation, I create a page named
something like changes27April2000.asp (I happen to use ASP, but this
should work for HTML pages, as well). On the main page of my site, I
check to see if the user has a cookie called something like
changes27April. If so, I just load the site as usual. If not, I write
that cookie to the user's machine and redirect to the
changes27April2000.asp page, where I have a description of the
relevant changes, including a link to the new version of the document.

That way, the user only gets bugged once about the changes. I also
have a list of links on the main page to all the change documents.


> It's for our company intranet.  What happens is I
> change a form on our site and the users are not
> refreshing their screen or clearing the cache to get
> the most recent copy, and they eventually fill out the
> 1st version of the form when I want them to use the
> current version.  I guess I could have the page
> refresh to a copy of the original page and just save
> it under a different name.
>
> example
> <META HTTP-EQUIV="Refresh"
>  CONTENT="5;URL=http://abc1.htm">
>
> Where abc.htm is the original page and abc1.htm is the
> revised page.
>
> There maybe a better way but I'm not sure.
>
> Peter

HWG: hwg-languages mailing list archives, maintained by Webmasters @ IWA