myriad — Mon, 04 Dec 2000 03:01:15 +0000

hi all,

You can do the above like this:

where 0 is the time in seconds between refresh
and url is the page to reload it can be the same page
or you can direct it to another.

I hope that this is what you wanted or I might have got
the wrong end of the stick.

HTH

steve

merlin — Tue, 28 Nov 2000 06:46:42 +0000

yes: how can i do that?
the above post is a scenario i wish to realize.

well, that's the problem with writing: it makes things much more complicated as they really are... especially, if there's one writing, who isn't this good in english...

Vincent Puglia — Mon, 27 Nov 2000 17:14:07 +0000

Hi,

I got that part, but is there still a problem? or a wish list?

Vinny

merlin — Mon, 27 Nov 2000 16:05:26 +0000

hi vinny

Quote: Originally posted by Vincent Puglia
I'm a little confused as to the current status of your problem, so if you can expound on the 1% you want.....

well, i can understand that...

i try it once again:
a user has our index.html on his screen for one day. during the day, we as webmasters make some changes on the page. now: right after we save the changes in index.html, the users page is reloaded. this means: there's kind of a signal (or whatever) that sends out the new page after we saved it. so there's no periodical reload in the file and still, the changes will be shown although the user never leaves our index.html.
are you with me? sounds pretty complicated, but in fact, it isn't, believe me!

Vincent Puglia — Sat, 25 Nov 2000 01:15:18 +0000

Hi alibababa,

Essentially, the 'expires' value tells the browser that the page has expired in the 'content' value of time (In the above case '0', or as soon as it is seen. You can put in different values for the content.

I'm a little confused as to the current status of your problem, so if you can expound on the 1% you want.....

Vinny

Mark Hensler — Thu, 23 Nov 2000 01:27:40 +0000

the page cannot be reloaded without any code or actual clicking of 'reload'

merlin — Wed, 22 Nov 2000 10:43:10 +0000

now i smell blood! and i'm getting insatiable...
following:
the user has our page on his screen. we make some changes on the page and when we save them, the page is reloaded ON the users screen. without any periodical reload ('setTimeout'). is this doable in an easy way?

but anyway, what i have now is 99% perfect, the rest would be heaven!

merlin — Wed, 22 Nov 2000 08:39:52 +0000

we only used the pragma-one. i added your 'expires' and now it seems to be working...
could you tell me what this tag is doing?

always interested in learning new things,
ali

Vincent Puglia — Tue, 21 Nov 2000 16:08:51 +0000

Hi alibababa,

Max's code will refresh as long as the page is active on the user's computer. If the user leaves the page and then returns the cache is used. If you want the newest page to be visible regardless, you will need to set a cookie as Max originally stated along with the meta tags.

When you used the meta tags, did they look like this?

Or, did you only use the pragma? It shouldn't matter where the page is cached. Also, you can tell your users to set the cache preferences in their browsers to no-cache.

Vinny

following question

merlin — Mon, 20 Nov 2000 12:28:12 +0000

but one following question:
takes this reload only in place when the user let the page on his screen?
or is it the other way round: the user visits the page, goes away for 5 minutes (to another page), we make some changes and when he comes back to our page, it has chaged 5 times (once/minute)? i think i'll try it out on my own...