Skip to content

Commit

Permalink
Fix typo in protol-spec-zh and minor error
Browse files Browse the repository at this point in the history
This commit is migrated from #2322.

Change-Id: Id205b5c74be0975d3c2f1648ca40b8dd210cebb7
Signed-off-by: jiangyaoguo <jiangyaoguo@gmail.com>
  • Loading branch information
jiangyaoguo committed Aug 2, 2016
1 parent 84431e3 commit f0d0885
Show file tree
Hide file tree
Showing 2 changed files with 140 additions and 139 deletions.
2 changes: 1 addition & 1 deletion docs/protocol-spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -1113,7 +1113,7 @@ func NewConsenter(cpi consensus.CPI) (consenter consensus.Consenter)

This function reads the `peer.validator.consensus` value in `core.yaml` configuration file, which is the configuration file for the `peer` process. The value of the `peer.validator.consensus` key defines whether the validating peer will run with the `noops` consensus plugin or the `pbft` one. (Notice that this should eventually be changed to either `noops` or `custom`. In case of `custom`, the validating peer will run with the consensus plugin defined in `consensus/config.yaml`.)

The plugin author needs to edit the function's body so that it routes to the right constructor for their package. For example, for `pbft` we point to the `obcpft.GetPlugin` constructor.
The plugin author needs to edit the function's body so that it routes to the right constructor for their package. For example, for `pbft` we point to the `pbft.GetPlugin` constructor.

This function is called by `helper.NewConsensusHandler` when setting the `consenter` field of the returned message handler. The input argument `cpi` is the output of the `helper.NewHelper` constructor and implements the `consensus.CPI` interface.

Expand Down
Loading

0 comments on commit f0d0885

Please sign in to comment.