Skip to content
This repository has been archived by the owner on Sep 26, 2019. It is now read-only.

Flatten IBFT Message API #757

Merged
merged 9 commits into from
Feb 4, 2019
Merged

Flatten IBFT Message API #757

merged 9 commits into from
Feb 4, 2019

Conversation

rain-on
Copy link
Contributor

@rain-on rain-on commented Feb 4, 2019

The IBFT messages have been flattened such that the content within the signed subtype can be accessed directly from the message interface.

IBFT2.1 requires that message content be separated, thus concepts
at the message level must not leak into the business logic - eg
RoundChangeCertificate should not be created by the
RoundChangeManager - rather an intermediate type is to be inserted.
@rain-on rain-on requested review from jframe and CjHare February 4, 2019 04:11
tmohay added 3 commits February 4, 2019 16:58
The IBFT messages have been flattened such that the content within the
signed subtype can be accessed directly from the message interface.
@Override
public BytesValue encode() {
final BytesValueRLPOutput rlpOut = new BytesValueRLPOutput();
rlpOut.startList();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are these encoded inside an additional list whilst some others also with a single e.g. Commit are writing the output as is?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are going to be required once the Block turns up being "piggybacked"

@rain-on rain-on merged commit 396e0cf into PegaSysEng:master Feb 4, 2019
@rain-on rain-on deleted the flat_msgs branch February 4, 2019 06:27
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants