Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

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
Collaborator

shuse2 commented Apr 22, 2022 •
edited
Loading

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
@shuse2 shuse2 mentioned this issue Apr 22, 2022
Closed
9 tasks
@shuse2 shuse2 moved this to Backlog in Lisk SDK Version 6.0.0 Apr 22, 2022
@milenagojkovic milenagojkovic added this to the Sprint 69 milestone May 9, 2022
@shuse2 shuse2 moved this from Backlog to In Progress in Lisk SDK Version 6.0.0 May 10, 2022
@shuse2 shuse2 mentioned this issue May 11, 2022
Merged
@shuse2 shuse2 moved this from In Progress to Pending Review in Lisk SDK Version 6.0.0 May 11, 2022
@shuse2 shuse2 closed this as completed May 16, 2022
Repository owner moved this from Pending Review to Done in Lisk SDK Version 6.0.0 May 16, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@shuse2 shuse2

Labels
framework
Projects
None yet
Milestone
Sprint 69
Development

Successfully merging a pull request may close this issue.

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