-
Notifications
You must be signed in to change notification settings - Fork 642
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
[Issue #417] gRPC design doc and protobuf models #593
Conversation
merged from upstream
…ice, CountDownLatch and PreDestroy hook
# Conflicts: # eventmesh-test/src/main/java/org/apache/eventmesh/http/demo/sub/service/SubService.java
…ice, CountDownLatch and PreDestroy hook
Very excited to see this initial shape, keep going... |
message RequestHeader { | ||
string env = 1; | ||
string region = 2; | ||
string idc = 3; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
region, namespace, idc, rack and so on. these tenant or geographic info should be carefully designed in our v2 version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BTW, any guys want to add comment for every field in protocol?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is V1 version of protobuf and we are experimenting this grpc transport feature.
Please review and comment on this set of header attributes and improve it in V2. @qqeasonchen @ruanwenjun
Thanks.
eventmesh-connector-plugin/eventmesh-protocol-grpc/src/main/proto/addressbook.proto
Show resolved
Hide resolved
+1 |
Fixes ISSUE #417.
Motivation
Modifications
Documentation