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.

Sign up for GitHub

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

Jump to bottom

Separate plugin communication and RPC endpoints handling #7135

Closed
Tracked by #7011
shuse2 opened this issue Apr 22, 2022 · 0 comments · Fixed by #7160
Closed
Tracked by #7011

Separate plugin communication and RPC endpoints handling #7135

shuse2 opened this issue Apr 22, 2022 · 0 comments · Fixed by #7160
Assignees
@shuse2
Labels
framework
Milestone
Sprint 69

Comments

@shuse2
Copy link
Member

shuse2 commented Apr 22, 2022 •
edited

Description

  • Update application to have a dealer and plugin to have a router (controller/channel implementation)
  • Separate the RPC endpoints handling from the plugin communication
  • Remove capability from controller to route plugin to plugin communication. (plugin will communicate to other plugin through the RPC endpoint)

Acceptance Criteria

  • Controller and RPC endpoints handling are separated
  • Update tests to reflect the changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shuse2 shuse2

Labels
framework
Projects
No open projects
Lisk SDK Version 6.0.0
Status: Done
Milestone
Sprint 69
Development

Successfully merging a pull request may close this issue.

Split RPC and controller then divide namespace - Closes #6991 LiskHQ/lisk-sdk
2 participants
@shuse2 @milenagojkovic