The context is as follows: The life of each task/thread is described by an "Actor" class, each task with a different execution context but with a common memory part.
In this common memory there is a data set of configuration properties. This area is controlled (in RW access) by a special task called Configurator. All other Actors can access in read-only mode to search and copy in local a subset of properties.
Access to the configuration by the Actors takes place at the start (after having been populated by the Configurator). Furthermore, if a Configurator runtime changes any properties it will warn all actors to update their copy locally.
Ultimately, the Configurator communicates with the actors through messages.
Is there a design pattern that models such a situation?
Aucun commentaire:
Enregistrer un commentaire