Greg Utas

Implement the capability described in ["Babbling Idiot Controls"](../blob/master/docs/RSC-Software-Design.pdf).

Re-inject messages that are still queued on a `Context` when it idles. The `Factory` or `Protocol` associated with a message must be consulted to decide whether to re-inject or discard...

It invokes `MsgPortPool.FindPeerPort`, which searches through all ports. A hash table that maps source addresses to destination addresses is one way to improve this. An entry would be created when...

Implement a web-based tool for generating most of the tedious "boilerplate" code for - a service's subclasses of - `Service`, `State`, `Event`, and `Trigger` (including many function bodies) - `Initiator`,...

Implement the journal file capability described in ["Escalating Restarts"](../blob/master/docs/RSC-Software-Design.pdf).

Implement the binary database capability described in ["Escalating Restarts"](../blob/master/docs/RSC-Software-Design.pdf).

Provide local and remote versions of OAM&P threads for nodes that do not have a disk or console. See ["Networked Threads"](../blob/master/docs/RSC-Software-Design.pdf).

As the POTS application undergoes distribution, the Control Node portion of the executable should support the following configurations, as described in ["Networking"](../blob/master/docs/RSC-Software-Design.pdf): - two Routing Nodes (load sharing): see #37...

As the POTS application undergoes distribution, the integrated Operations/Control Node portion of the executable should propagate data changes to the subset of nodes that require it, as described in ["Data...

Once Service Nodes are running in a paired cold standby configuration, the framework described in ["Checkpointing and Failover"](../blob/master/docs/RSC-Software-Design.pdf) should be implemented to support a warm standby configuration. See #39 and...