`TDTopezServer reset` wipes out the instances of TDTopezServer
associated with tODE client sessions ... the TDTopezServer instance is
sent messages via ClientForwarders from the Pharo client ... not all
interactions between the client and server send messages to the
TDTopezServer instance, but those that do would fail... The `topez`
message returns a TDTopezServer instance obtained from the instanceMap
... it looks like it "self repairs" so tODE proably survives across
reset boundaries, but things linke command history might not ...
Does this help?
Dale