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

Introduce opaque service endpoint id #413

Merged
merged 1 commit into from
May 17, 2023

Conversation

slinkydeveloper
Copy link
Contributor

@slinkydeveloper slinkydeveloper commented May 16, 2023

Fix #405

Copy link
Contributor

@tillrohrmann tillrohrmann left a comment

Choose a reason for hiding this comment

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

Thanks for creating this PR @slinkydeveloper. The changes look good in general. I had a question whether we are implicitly relying on grpc internals.

src/common/src/opaque.rs Outdated Show resolved Hide resolved
src/common/src/opaque.rs Outdated Show resolved Hide resolved
src/common/src/opaque.rs Outdated Show resolved Hide resolved
Copy link
Contributor

@tillrohrmann tillrohrmann left a comment

Choose a reason for hiding this comment

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

LGTM. +1 for merging after adding an explanation where the invariants of the service name come from.

@slinkydeveloper slinkydeveloper merged commit c334c6e into restatedev:main May 17, 2023
@slinkydeveloper slinkydeveloper deleted the issues/405 branch May 17, 2023 09:25
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.

Add opaque service token to identify service invocation (service name, key, invocation id)
2 participants