Stuck in a Time Warp!

[kreynolds]

Re: New workaround!

I've found a new workaround that seems to be much more reliable than the old workarounds--but at a price.

Charles, I've had the same problem on my mac as well (netscape), but your solution also worked for me. Come to think of it, I've had this problem for a few months now, but since my Mac is on my left and I've got a PC on my right, I just hopped over.

Anyways, this temp fix definately works.

 

[Blacksway]

Time to add the no-cache headers me thinks...

 

[EricNoah]

Ok, I'm going to try it. *crosses fingers* -- here's hoping it doesn't crash the server...

 

[EricNoah]

Blech, turned that setting back to off. Could be a coincidence but I experienced a massive slowdown right after "no-cache" option was turned on. I may try it later when it's not so busy...

 

[Henry]

Re: New workaround!

I've found a new workaround that seems to be much more reliable than the old workarounds--but at a price.

I've set my browser's cache space to 0, and set it to check the cache against the server page every time I visit the page. (In Netscape 6.1: Edit->Preferences->Advanced->Cache; set disk cache to 0, set "Compare the page in the cache to the page on the network:" to "Every time I view the page.") Oh, yeah, I also purged the disk cache. (There's a button for that in the cache preferences.)

Charles, kreynolds, I know you've probably already tried this, but for verification, have you tried to change ONLY the "Compare" settings, leaving the disk cache size alone? If it works, comparison is a fraction of the time compared to grabbing the page new.

It sounds as though Web caching on the Macs in question is using either some sort of limited character comparison, or something else besides checksumming to compare with - but take that as an opinion unfamiliar with macs or netscape.

 

[CharlesRyan]

Re: Re: New workaround!

Charles, kreynolds, I know you've probably already tried this, but for verification, have you tried to change ONLY the "Compare" settings, leaving the disk cache size alone? If it works, comparison is a fraction of the time compared to grabbing the page new.

I gave it a try, but it didn't work. Most of the fora I visit are now frozen at 2:03 PM; if I use the old workaround (maneuvering through the Forum Jump menu) I can update them. I'm setting my cache back to 0; looks like I'm stuck with that solution for the time being. . . .

 

[Fast Learner]

An old web programmer's trick is to put "something@" before the url. For example you could put "bubba@enworld.cyberstreet.com". Your browser will think that this is a different page than "enworld.cyberstreet.com" and so will not use the cache.

The only trick is that you need to come up with a new word every time. Still, it should work perfectly.

 

[Quartermoon]

Re: New workaround!

Hi!

Mac OS 8.6, Netscape 6, home dial-up (no firewall, network, blah blah)

I've had this problem ever since the switch to the new boards last year. (Just ask Piratecat!) The worst what when I would post a reply, and it would send me back to the end of the topic, but my post wouldn't show! )I had a rather thorough chat with a guy at vBulletin about it, and he was pretty clear that it's not them...but could never really address why it doesn't happen anywhere else that uses vB. I think the dialogue is on ther help forum somewhere...

I've set my browser's cache space to 0, and set it to check the cache against the server page every time I visit the page.

This is essentially how I solved the problem, but I left the "check cache against server" to "Automatically." At least in my version, Netscape differentiates between memory cache, which it keeps in current memory during a single browsing session, and disc cache, which it stores on your hard drive. So just setting the disc cache to 0 prevents the cache from your last session from being kept.

This means that, yes, the first time a page loads, it takes a while, but it's still in memory if you go back to it---yes, this is a problem here in these boards, but not anywhere else, so I find it a good compromise. I then go ahead and use the usual work-arounds to ensure I get the freshest page here when I have a problem (which isn't as often anymore...go figure).

The only thing that really gets to me is that before the move, this never happened. So something changed somewhere, but who knows if we will ever find it.

BTW, if you look really, really, really close, you can tell that Hacker Kulp is using a Mac. I blame him.

 

[Piratecat]

Everyone blames me. sheesh.

 

[CharlesRyan]

Any news?

Any progress on this issue? I'm still using the no-cache workaround, and it still works, but sheesh is it sloooowwww. . .