Skip to content

Conversation

@stevegury
Copy link
Member

_Problem_
There is an error in the Error frame, the error codes used for APPLICATION_ERROR,
CONNECTION_ERROR, REJECTED, CANCELED and INVALID were invalid.

_Solution_
Update the constants.
I don't think it requires doing any version bump, since the error code was not used
prior to #150.

_Modification_
I also took the oportunity to review the frame package and update it to the Java
code style.

***Problem***
There is an error in the Error frame, the error codes used for `APPLICATION_ERROR`,
`REJECTED`, `CANCELED` and `INVALID` were invalid.

***Solution***
Update the constants.
I don't think it requires doing any version bump, since the error code was not used
prior to #150.

***Modification***
I also took the oportunity to review the `frame` package and update it to the Java
code style.
public static final int APPLICATION_ERROR = 0x0021;
public static final int CONNECTION_ERROR = 0x0101;
public static final int APPLICATION_ERROR = 0x0201;
public static final int REJECTED = 0x0022;
Copy link
Member

Choose a reason for hiding this comment

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

why not fix Rejected?

Copy link
Member Author

Choose a reason for hiding this comment

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

oversight.

stevegury added a commit that referenced this pull request Jul 15, 2016
It should have been fixed in #151, that was an oversight from my part.
@stevegury stevegury deleted the stevegury/error-code-invalid branch July 15, 2016 22:30
robertroeser pushed a commit that referenced this pull request Jul 26, 2016
It should have been fixed in #151, that was an oversight from my part.
xytosis pushed a commit to xytosis/reactivesocket-java that referenced this pull request Aug 6, 2016
It should have been fixed in rsocket#151, that was an oversight from my part.
ilayaperumalg pushed a commit to ilayaperumalg/rsocket-java that referenced this pull request Dec 26, 2017
* Make Resume Token Not Present If Flag Not Set

This makes the behavior for resume token similar to metadata. If the flag is not set, then the bytes will not exist in the payload.

This is discussed in rsocket/rsocket#149

* 65,535 not 65,536
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.

4 participants