-
Notifications
You must be signed in to change notification settings - Fork 1
feat: nitro-rpc proto and golang draft implementation #2
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
Conversation
nitro_rpc/web/server.go
Outdated
|
|
||
| state := RPCState{ | ||
| RequestID: req.Req.GetRequestId(), | ||
| Timestamp: req.Req.GetTimestamp(), |
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.
Shouldn't we set a new timestamp here, so that an external party can calculate how much time a response took place to calculate?
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.
As I discussed with @mnaichuk timestamp will be later generated by server, so that is TBD
|
|
||
| privateKey, err := crypto.GenerateKey() | ||
| require.NoError(t, err) | ||
| ss := signer.NewLocalSigner(privateKey) |
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.
Why do you shorten signer to ss?)
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.
Because signer is the name of the package, and ss stands for stateSigner, I could instead use rename for package as signer_pkg
No description provided.