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

MessagingService component #1

Closed
timiblossom opened this issue Oct 31, 2013 · 1 comment
Closed

MessagingService component #1

timiblossom opened this issue Oct 31, 2013 · 1 comment

Comments

@timiblossom
Copy link
Contributor

We should have this component first as one of the backbone components to help communication between nodes. Similar in Cassandra, this component is leveraged in Gossiping as nodes exchanges gossiping messages asynchronously. Also, it is used in asynchronously exchanging other kinds of messages in Cassandra like Merkle tree requests, cluster snapshot taking, mutation messages, data repair streaming requests, and many others. I am creating this issue just for building the MessagingService.

@ghost ghost assigned timiblossom Oct 31, 2013
@timiblossom timiblossom removed their assignment Mar 11, 2014
@timiblossom
Copy link
Contributor Author

Done

shailesh33 added a commit that referenced this issue May 25, 2015
anujphadke pushed a commit to anujphadke/dynomite that referenced this issue Sep 18, 2020
added default thrift port 9160 and default cassandra being localhost
anujphadke pushed a commit to anujphadke/dynomite that referenced this issue Sep 18, 2020
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

No branches or pull requests

1 participant