Hi, I'm new to web development and have been given a task at work to build dynamic pages displaying internal system info on TV screens in a public area, so the environment is very specific - output to a large Flatpanel TV, browser is FireFox)
I'm not sure if I'm posting to the right forum, so apologies in advance if I've picked the wrong one.
The pages are specifically designed to be displayed at 1920x1080
I have a problem with one of the pages.
There is an ASP.NET element to the page, which on Page Load fetches some data from a database (recent visits by Field operatives to customers) and inserts it as array elements into a script element in the page header.
Once the script has run through all the items in the array it reloads the page (using
window.location.href = strURL;
as the command, where strURL is previously declared and assigned the URL of the page).
I've got access to the IIS logs for the server, and I see nothing unusual there (the request status shows as 200), although I don't really know much about interpreting them.
Can anyone suggest anything I could look for to give me a clue as to what's causing this behaviour?
Hi, Firebug did not pick up any errors when the problem recurred.
However, watching the Net part of the console to see what the request & response headers looked like gave me an idea.
The page referenced the same large (1920x1080) PNG image 13 times as background to various DIV elements.
I had assumed that once the image had been retrieved from the server it would be kept as cache and only fetched again if the original image file changed. This appears not to be the case.
I've eliminated that repeat reference and used smaller crops of the main image where it's not the actual background of the page, but is used in elements higher up the z-index (to give the illusion of text disappearing into the background), and it's been running for much longer than it used to take to lock up.
I've also made the database query much more efficient, although I was convinced the ASP.NET part of the process was not the problem (the full HTML page would transfer, and could be inspected through the browser, and I've got other pages with queries that take much longer, and return much larger datasets that aren't a problem).
If it runs OK over the weekend I'll close the thread off as resolved.