Subject:
|
Re: Browser locking up with big threads
|
Newsgroups:
|
lugnet.admin.general
|
Date:
|
Sat, 1 Apr 2000 19:10:45 GMT
|
Viewed:
|
633 times
|
| |
|
|
Todd Lehman wrote in message ...
> The page you're loading is the output of a CGI script (rather than a static
> HTML page), so although it stays in your browser's cache for when you hit • the
> Back and Forward buttons, each time you re-invoke it via a click of a "go • to
> location," it regenerates the page. The server doesn't know (or, rather,
> doesn't bother to check, because doing so would be a real mess) what has
> changed, if your browser sends If-Modified-Since header as part of its HTTP
> request, and similarly it doesn't respond to HEAD.
Hmm, would there be something to being able to know the "modified" time of
stuff on Lugnet? It might be harder for the newsgroup displays, but for
relatively static data like Pause, it could be real beneficial.
Frank
|
|
Message has 1 Reply:
 | | Re: Browser locking up with big threads
|
| (...) it's possible (and recommended), that cgis put a meta EXPIRES tag, which tells the browser when to check the page again... for pause, this could be set for at least a week... for other things, like the spotlight, a day might be better... :) (...) (24 years ago, 2-Apr-00, to lugnet.admin.general)
|
Message is in Reply To:
| | Re: Browser locking up with big threads
|
| (...) I get that all the time with Netscape Navigator -- all versions. It's always had a terrible time displaying super-complex tables. I'll bet if you load it up into Mozilla or MSIE5 it'll display a lot quicker. I don't know what to offer as (...) (24 years ago, 1-Apr-00, to lugnet.admin.general)
|
7 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
