Boris Zbarsky <[EMAIL PROTECTED]> wrote in message news:<b1uek5$[EMAIL PROTECTED]>... > Chris Sobotkiewicz wrote: > > However, sometimes things go nuts and > > a single user can cause my server to grind to a halt. What do I do? > > I'd hate to deny Netscape users access to the play button, but its > > getting to that point! > > So your server grinds to a halt because of requests to see whether the > image has _changed_? > > You _are_ seeing the problem in Mozilla, right? Not just in Netscape? > If so, what are your cache settings in Mozilla? (memory cache size and > policy for rechecking content validity are the ones relevant here)
No, for awhile, Netscape/Mozilla will send If-Modified-Since headers and I will appropriately respond to these with "HTTP/1.1 304 NOT MODIFIED". This of course is such a small load on my server that I don't really care. However, at some point, these stop getting appended to the header and all of a sudden my server gets flooded with real image requests. I have tried all of the advanced cache policies. I'm currently on "Never" check back with server, but it seems to do nothing for me. We are currently exploring other alternatives to the animation loop script. Instead of doing the usual document.image.src = imgArray[playIndex].src, it seems using z-ordering of these images does not hit the server at all. More work for me though :(. Chris Chris
