Simple Timer Demo with JavaScript


I visited an auctioneer website at my brothers request that was working on what seem to be some time of bot auction.  There was this box that was logging messages live and anyone could bid on the item being auction.  This was just like a real live auction, except it was done over the web…

A typical log would like like this

  • Auctioneer:  Now bidding for 7.50
  • Auctioneer: This bid is about to close
  • Auctioneer: This bid is about to close
  • Auctioneer: Now the bidding for 8.00
  • Auctioneer: This bid is about to close
  • Auctioneer: This bid is about to close
  • Auctioneer: Item sold to bidder #349 for 8.00

That got me thinking about timers in javascript.  Timers, I assume is something that I have to understand in order to continue refreshing the page with everyone’s bids.  It could also be done with async call backs possibly but for my experiment I wanted to try out timers.  I know I also have to understand AJAX and connect it to a back end for fetching.  So I decided to create a demo.  It is a simple demo but just little things were kicking my butt like having bugs with undeclared variables and such. 

Anyway I got the whole thing working and posted to my webexperiment (followmetotheweb page.

You can check it out here

http://followmetotheweb.apphb.com/SetIntervalDemo.html

You can view the code as by selecting view source.

It is pretty much a beginner's exercise but since I went through all the trouble I figured I'd share it.

Comments

Post a Comment

Popular posts from this blog

Putting Files on the Rackspace File Cloud

Recently, I’ve been playing around with Asp.Net MVC and I (along with some friends) am creating an Asp.Net MVC application that can access files from our website. This means that files must display on the site as well as provide a way to download/upload them. I won’t give away all the details of the project but I will say this: Sharing photos is one of the driving forces for our project.  The files are only image type files( jpg, etc) The files must be uploaded by the users and stored somewhere within our system.  We don’t necessarily know at this time how much storage space we need but we think that we will need a little at first but possibly a lot more down the road. This means that the storage of these files must be scalable. The uploading of files must be controlled by our system.  Right off the bat we started our application and were uploading files to the web server with no problem.  We only did it this way to kind of prove our system model. We were just basically writing
Read more

Setting Up XnaMobileUnit to run unit tests in Windows Phone 7 XNA Games

Image
Introducing XnaMobileUnit I decided to roll my own unit test framework for Windows Phone 7 XNA games.   I have a couple of reasons why I decided to roll my own.  Among them was the fact that you cannot reference regular .Net assemblies from Windows Mobile Framework.  That means that referencing NUnit was out of the question.  Also using some of the other libraries that can be used for Silverlight Applications didn't quite feel right for me. The framework that I have created, XnaMobileUnit, is very simple to use and provides all the necessary functionality to run unit tests.  I am still working on the framework to provide a few more capabilities and features, but for the most part it is ready to use out of the box.  XnaMobileUnit is open source licensed under the Apache 2.0 License and can be downloaded from http://code.google.com/p/xna-mobile-unit/ .  I recommend downloading the latest source and compiling it then referencing the new DLL. Otherwise you can simply download the l
Read more

Reasons to Stay Away from CSLA

We've been using CSLA - Component-based Scalable Logical Architecture in a product for approximately one year and while it solves quite a few problems it violates some major good practices. No Clear Separation of Layers While at the time that we chose CSLA we knew very little about domain driven design, it is no excuse for the framework to possess the data access layer within the business object. This makes it extremely difficult to separate the concerns. As a result, it is difficult to mock the data-access layer creating many problems when attempting to perform unit tests. This also puts the additional responsibility of data access on the business object class, violating the Single Responsibility Principle( SRP ). Data access layer should be totally separated from the business object period. Having the data access within the within the BO class is not the only additional responsibility placed on the class but is the most significant one I can think of. No Context Validation
Read more