Master/Slave
From TBwiki
(Difference between revisions)
(Creation) |
(→Example) |
||
| (2 intermediate revisions by one user not shown) | |||
| Line 1: | Line 1: | ||
== '''Master''' == | == '''Master''' == | ||
| − | Master is a module state that | + | Master is a module state that indicates which module instance is taking decisions for the system. |
== '''Slave''' == | == '''Slave''' == | ||
| − | Slave is another instance state that is taking orders from the master application. The slave instance can still | + | Slave is another instance state that indicates the module is taking orders from the master application. The slave instance can still exectute some actions as opposed to [[Active/Standby]] modules where the standby module does not take any actions. |
== '''Example''' == | == '''Example''' == | ||
| − | Example: tboamapp is a master/slave type application. The master tboamapp | + | Example: tboamapp is a master/slave type application. The master tboamapp makes most decisions, but the slave tboamapp is still responsible to start applications on its host. |
Latest revision as of 14:43, 30 December 2009
Master
Master is a module state that indicates which module instance is taking decisions for the system.
Slave
Slave is another instance state that indicates the module is taking orders from the master application. The slave instance can still exectute some actions as opposed to Active/Standby modules where the standby module does not take any actions.
Example
Example: tboamapp is a master/slave type application. The master tboamapp makes most decisions, but the slave tboamapp is still responsible to start applications on its host.
