You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The introduction of SimulationContext was important to facilitate the creation of custom context classes. Nevertheless, it's a shame that at the moment, you have to decide on one concrete subclass of SimulationContext. For example, you cannot combine the functionalities of SimulationMsrContext and SandboxContext. For further possible conflicts, refer to #14. It would be great to eliminate this limitation.
Possible approaches:
Composition (e.g. a subclass of SimulationContext, PluggableContext, defines hook and forwards them to a Simulator instance)
Chain of Responsibility vs list of simulator objects to be invoked in series ("explicit CoR")
Simulator implements the Chain of Responsibility pattern to make multiple customizations to the simulation engine combinable. Additionally, SimulationMessageSendRecorder (8f12aff) and Sandbox (fddeb9a) are ported to this new framework (for Sandbox, the new version is called Sandbox2). Tests exist as well, of course.
Closes#15.
The introduction of
SimulationContext
was important to facilitate the creation of custom context classes. Nevertheless, it's a shame that at the moment, you have to decide on one concrete subclass ofSimulationContext
. For example, you cannot combine the functionalities ofSimulationMsrContext
andSandboxContext
. For further possible conflicts, refer to #14. It would be great to eliminate this limitation.Possible approaches:
SimulationContext
,PluggableContext
, defines hook and forwards them to aSimulator
instance)Keep performance in mind (see #13)!
The text was updated successfully, but these errors were encountered: