Sharing an asp.net/c# counter with a peer review request.

[Rick]

Hello,

I'm six months into asp.net/c# and enjoying it. I needed to code a "simple"
high performance counter... a couple weeks later and a lot of learning I
think I did it.

Many lesson lessons learned including: static objects vs. cached objects,
performance of asp.net, strong typing collections, collection locking, and
using the very helpful System.Timers.Timer();

Because I was able to learn so much from those who freely share their code
online I have in turn shared this counter code. For those with the time and
interest I welcome, heck encourage, some peer review.

Click on the "An Enterprise Counter" link at http://coders.eproof.com.

Thank you,

Rick

 

[Cowboy \(Gregory A. Beamer\)]

Add some graphical ability, and you may be able to sell it. ;->

I did not have a lot of time, but from my brief look, it looks sound. If I
get a chance, I will go a bit deeper.

Suggestion: Consider config changes for the counter component. As it is used
in ASP.NET, you can set it up to pull from the web app config file. Some
potential config settings:
a) where to save the data
b) Ability to set a list of "live" and "test" servers (noticed you had that
hard coded)

There are probably a few more configurable items you can think of. Right
now, you are sharing the source and allowing the user to set this (great use
of comments; noobs to .NET will love your code), but config will make it
more reuseable, as a person will not have to recompile to set these
settings.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

**********************************************************************
Think Outside the Box!
**********************************************************************