-
Notifications
You must be signed in to change notification settings - Fork 26
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
book/architecture: RPC handlers and related #341
base: main
Are you sure you want to change the base?
Conversation
The handlers (functions that map requests into responses) are / can be generic with `cuprate-rpc-interface`. | ||
|
||
The main handlers used by Cuprate is implemented in `cuprated` itself, it implements the standard RPC handlers modeled after `monerod`. |
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.
The main handlers used by Cuprate is implemented in `cuprated` itself, it implements the standard RPC handlers modeled after `monerod`. | |
The main handlers used by Cuprate are implemented in `cuprated` itself, it implements the standard RPC handlers modeled after `monerod`. |
The main handlers used by Cuprate is implemented in `cuprated` itself, it implements the standard RPC handlers modeled after `monerod`. | ||
|
||
- JSON-RPC handlers: <LINK_TO_FILE> |
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.
- JSON-RPC handlers: <LINK_TO_FILE> | |
- JSON-RPC handlers: <LINK_TO_FILE> |
lol
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.
These links do not exist yet, they depend on #355.
What
Fills RPC sections in the architecture book to cover the changed made in #244.