As of today, bids on Bidazzled need to reach our server before time reaches zero (as opposed to our prior 1.5 seconds).
This move is designed to make Bidazzled simpler and easier for people to use. Here is what is going to happen:
- Countdown clock will start at 16 seconds (not 18 seconds) and will count down until a bid is placed. At zero seconds, we need to check and see if any bids have been received at the server (it takes some time, not much for the bid to go to and back from the server).
- Right at zero seconds we will display a “Checking Server For Bids” message. This should only appear for 1 second. If a bid was received, the countdown clock will resume. If not bid is received, the server sends out the final results of the auction and a
- Auction Closed page is displayed with a summary of the winners bids.
Note, some individuals have reported seeing “Ended” and then the auction coming back to life. This is due to a lag which is not uncommon on the internet but in most cases (99%) it is the result of the user running other programs, having multiple windows open or even just 1 additional window on an auction site. These programs require CPU time and can rob your system of the needed updates to keep Bidazzled up to date.
Remember, if bidding on Bidazzled – Prepare yourself and your computer to do so. Follow our optimal computer settings (found on this blog) and the home page of Bidazzled. A quick check list would be:
- A fresh reboot is a great thing
- Use Firefox, it handles javascript and Ajax faster than IE
- Open a single fresh window
- Do not download large files or multimedia while on Bidazzled
- Do not use other CPU intensive programs