Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add precisions about versioning #15

Merged
merged 1 commit into from
Feb 25, 2020
Merged

Conversation

hug-dev
Copy link
Member

@hug-dev hug-dev commented Feb 25, 2020

Precises the goal of each version in Parsec. See
parallaxsecond/parsec#105 for more details.

Signed-off-by: Hugues de Valon hugues.devalon@arm.com

@hug-dev hug-dev added the invalid This doesn't seem right label Feb 25, 2020
@hug-dev hug-dev self-assigned this Feb 25, 2020

1. Client requests a Ping operation using the wire protocol version `1.0`.
2. Service responds with the highest wire protocol version supported `x.y`.
3. Client can now use wire protocol version `x.y` for further requests.
Copy link
Member

Choose a reason for hiding this comment

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

Client can now use any wire protocol version below x.y - trying to cover the case where the client might only support a lower version

Copy link
Member Author

Choose a reason for hiding this comment

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

Sure, will change!

- Header size: a 16-bit unsigned integer whose value is the size of the **remainder** of the header
in bytes (once the magic number and header size fields have been consumed). Consumers **must**
use this field to consume the correct number of bytes of header from the input stream, rather
than use this specification to deduce the header size.
than use this specification to deduce the header size. This field will remain the same across
Copy link
Member

Choose a reason for hiding this comment

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

The last phrase sounds a bit confusing - i.e. sounds a bit like the value will stay the same, but I don't know how to fix that right now.

Copy link
Member Author

Choose a reason for hiding this comment

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

Will modify to make it more clear.

Precises the goal of each version in Parsec. See
parallaxsecond/parsec#105 for more details.

Signed-off-by: Hugues de Valon <hugues.devalon@arm.com>
Copy link
Member

@ionut-arm ionut-arm left a comment

Choose a reason for hiding this comment

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

👍

@hug-dev hug-dev merged commit f560b09 into parallaxsecond:master Feb 25, 2020
@hug-dev hug-dev deleted the versioning branch February 25, 2020 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants