Greg Utas

Once the checkpointing framework exists and Service Nodes are running in a warm standby configuration (#42), enhance the Service Nodes and the Control Node to support failover. See ["Checkpointing and...

Support the additional overload control strategies described in ["Handling Overload"](../blob/master/docs/RSC-Software-Design.pdf). `Factory` subclasses decide which strategy to use.

Implement the capabilities described in ["Session Testing"](../blob/master/docs/RSC-Software-Design.pdf).

When a context is being traced, start the same trace tools on the context(s) with which it is communicating, as described in ["Trace Tool Propagation"](../blob/master/docs/RSC-Software-Design.pdf).

As the system becomes distributed (see #37, #38, and #39), support tracing in multiple nodes as described in ["Trace Tool Networking"](../blob/master/docs/RSC-Software-Design.pdf).

When an exception occurs, the stack is disassembled to display the chain of function calls that led to the exception. Enhance this to also display each function's stack variables.

Enhance `TransTracer` so that, when it traces multiple sessions, it can aggregate those with identical message sequences. This is useful for seeing the average I/O and transaction cost of each...

Implement a trace tool for recording messages sent/received by threads. A likely approach is to introduce a base class that would be used by both `BuffTrace` and a new trace...

Implement `startat` and `stopat` options so that function tracing starts/stops when a specific function is invoked, either by a specific thread, type of thread, or faction. It could also be...

Track how much time each `Context` is using to detect CPU hogs (e.g. a messaging loop between two contexts). Kill a context that used more than _x_% of the CPU...