This example builds on the simpler
Timer Example Server 1 and shows you how to build another server that uses timers to generate periodic events. The basic structure is very similar to the
Thread Pool Simple Protocol Server example uses concepts that were explained in the
Timer Example Server 1 example. You should go and read about those first and have a good understanding of how everything fits together. This document will only cover the differences between this and the earlier examples.
This example is shipped with all licensed versions of The Server Framework and it requires the core server framework libraries (see
here for licensing options). You can always download the latest version of this example from
here; and although you will need the correct libraries to be able to build it you can look at the example code and see how it works and perhaps get ideas from it. A compiled, unicode release, build of this example is available on request if you require it for performance analysis of the framework.
The main differences between this server and the
Timer Example Server 1 are that this server uses stores its per connection timer in its per connection user data, the server itself has two non connection related periodic events that cause broadcasts to all connected clients and all timer events are marshalled to the business logic thread pool so that they don't block the timer queue thread during processing.
