Grpc-based remoteDb - #788
Merged
Merged
Conversation
JekaMas
reviewed
Jul 25, 2020
Contributor
|
I think it can be useful not to expose transactions to the client at all, and yes, inconsistent data can be detected on the client side |
AskAlexSharov
force-pushed
the
grpc
branch
7 times, most recently
from
July 27, 2020 04:33
908653a to
ca3bf01
Compare
AskAlexSharov
force-pushed
the
grpc
branch
5 times, most recently
from
July 27, 2020 11:10
aecd1c5 to
0c3a36a
Compare
battlmonstr
pushed a commit
that referenced
this pull request
Sep 14, 2023
cffls
pushed a commit
to cffls/erigon
that referenced
this pull request
Jul 25, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
kv.proto.Other changes:
--http.port--remote-db-addrto--private.api.addr- because GRC can serve more than 1 service on same port (probably we will add more private apis later)