Suppose you've written a great n-tier application in ASP.NET and you want to extend it to perform scheduled tasks, such as sending e-mail to selected users in the database every two hours, or regularly analyzing the data in the ASP.NET cache for application health monitoring. You don't want to throw away your object model from your ASP.NET application or create too many dependencies between a separate scheduler and the ASP.NET application, so how can you avoid this but still have these apps work together? In .NET Framework-based applications, timers are frequently used to perform activities at scheduled intervals, so using one would seem to ..
