Skip to content

add optional little_endian argument to new_protocol method. Also, pas…#64

Open
MattFriedman wants to merge 1 commit intoMarketSquare:masterfrom
MattFriedman:master
Open

add optional little_endian argument to new_protocol method. Also, pas…#64
MattFriedman wants to merge 1 commit intoMarketSquare:masterfrom
MattFriedman:master

Conversation

@MattFriedman
Copy link

…s the value of this argument to the Protocol constructor. this gives the user of the new_protocol the ability to specify byte order when creating the protocol

This is related to the issue I created earlier. See: #63

…s the value of this argument to the Protocol constructor. this gives the user of the new_protocol the ability to specify byte order when creating the protocol
@jussimalinen
Copy link
Contributor

Thanks for the pull request! We have tried to keep the documentation and tests up to date with new features when ever possible.

Could you consider also making an acceptance test for this? At the most simple form it could be a test where you define a very simple little endian protocol for server. Then client sends something in raw binary hex and server receives it so that the contents are reversed for each field?

But you could define the protocol and message format for the server there in within that test if you prefer.

The tests are in atest folder. A bit difficult to follow some of them, but you can look at for example https://github.com/robotframework/Rammbock/blob/master/atest/protocol_templates/define_protocol.robot for reference.

I can also write the test but then it will take a moment.

@MattFriedman
Copy link
Author

MattFriedman commented Feb 22, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants