AJAX Loop Works in FF and Safari, but NOT IE
 

I am having some trouble in Internet Explorer

You all know that dreaded prompt message you get if a website starts slowing down your computer because of a loop?

Well I have been working on a website, got it to work perfectly in Firefox and Safari.

BUT, in Internet Explorer it refuses to work.

The website is called Auction 4 Pennies
It was inspired by Swoopo, a auction website with timers.

I wanted to attempt creating the website without cheating (viewing available source) and without having to purchase a $800 clone.

Right now how it is setup is:
-The page loads
-Then the page uses AJAX to retrieve the Products Page
-On the Products Page it has Current Timers and Current Highest Bidder with Amount
-After that is all loaded, it will loop every second after that, but not reloading all products, just pulling information from the database on another page (using ajax) and creating JS with the information pulled. The returned JS then is executed to reset the Timers and Highest Bidder (in case of a change)

I know there is a Fix to edit the registry on the computer, but there are problems with that.

1. The fix only works on the local machine.
2. The timers on the page take between 15 and 60 seconds to change.
3. The page is still so slow and freezes IE even tho the prompt does not display.

Are there any suggestions to fix the IE problem?

You might be better off looking into COMET because a ping a second is going to add up to a nice DOS if your user count increases and your servers do not.

YOu make an Ajax call to update the clocks? why? That could be 100% js

Your other call returns a 500.

Eric

That seems to be the only and best answer I've seen in the past 3 weeks.

Is there a website or anything I can get a quick feel for Comet?

The reason it uses ajax to call the another file is to check if there has been a change.

The website is for auctions, similar to Swoopo.com

If someone bids, the timer goes up 15 seconds.
And we need it to update on everyones browser without having to refresh the entire page.

Not just that one users browser that placed a bid, if we could do that we would but the problem lies in with, if someone bids the price goes up, naturally, but if it doesn't update the bid price (which gets changed same as timer) on everyones browser, they will end up bidding lower than the highest bidder unless they refresh right before they bid.