Changes between Version 5 and Version 6 of MasterSlaveCommunication
- Timestamp:
- 05/31/12 10:30:01 (12 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MasterSlaveCommunication
v5 v6 18 18 After that the master requests information about the slave, via the remote methods {{{ getSlaveInfo}}}, {{{ getVersion}}}, and {{{ getCommands}}}. 19 19 20 The SlaveInfo currently consists of the contents of the slave's info/ directory.[[BR}}20 The {{{SlaveInfo}}} currently consists of the contents of the slave's info/ directory.[[BR]] 21 21 This also contains the keys[[BR]] 22 22 {{{environ}}}: copy of the slaves environment[[BR]] … … 54 54 55 55 The proposed protocol is message-based rather than RPC based. 56 The protocol would be versioned. The initially planned changes are shown below. [[Image(ProposedSequenceDiagram.png)]]56 The protocol would be versioned. The initially planned changes are shown below. 57 57 58 Changes will include reducing the number of roundtrips, support for several masters, a busy-signal from the slave, protocol versioning and other improvements. 58 [[Image(ProposedSequenceDiagram.png)]] 59 60 Initial changes will include reducing the number of roundtrips, a busy-signal from the slave, protocol versioning, graceful handling of disconnections, etc. Future changes would include support for several masters, etc.
![[Buildbot Logo]](/chrome/site/header-text-transparent.png)