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

Cleanup of the transport request/response messages #6834

Closed
wants to merge 1 commit into from
Closed

Cleanup of the transport request/response messages #6834

wants to merge 1 commit into from

Conversation

uboness
Copy link
Contributor

@uboness uboness commented Jul 11, 2014

Now both TransportRequest and TransportResponse inherit from a base TransportMessage that holds the message headers and also now added the remote transport address (where this message came from).

/**
*
*/
public abstract class TransportMessage<TM extends TransportMessage<TM>> implements Streamable {
Copy link
Contributor

Choose a reason for hiding this comment

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

It seems to me like this class would be simpler if headers were always not null (and just empty in case there is no header).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I agree

Copy link
Contributor

Choose a reason for hiding this comment

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

Nevermind, I just noticed this is required for bw compatibility.

Copy link
Contributor

Choose a reason for hiding this comment

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

However, can you make this class pkg-private?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't think it needs to be package private (some things in the codebase may work on messages regardless of whether it's a request or response)

Now both TransportRequest and TransportResponse inherit from a base TransportMessage that holds the message headers and also now added the remote transport address (where this message came from).
@jpountz
Copy link
Contributor

jpountz commented Jul 11, 2014

LGTM

@s1monw s1monw added v1.4.0 and removed v1.3.0 labels Jul 14, 2014
@s1monw
Copy link
Contributor

s1monw commented Jul 14, 2014

LGTM too

@s1monw s1monw removed the review label Jul 14, 2014
@uboness uboness added v1.3.0 and removed v1.4.0 labels Jul 14, 2014
@uboness
Copy link
Contributor Author

uboness commented Jul 14, 2014

closed by 25a21c6

@uboness uboness closed this Jul 14, 2014
@clintongormley clintongormley changed the title Cleanup of the transport request/response messages Internal: Cleanup of the transport request/response messages Jul 16, 2014
@clintongormley clintongormley changed the title Internal: Cleanup of the transport request/response messages Cleanup of the transport request/response messages Jun 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants