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.

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

Rethink some sub-systems of js-waku to be setup as libp2p services #1392

Open
danisharora099 opened this issue Jun 3, 2023 · 1 comment
Open

Comments

@danisharora099
Copy link
Collaborator

danisharora099 commented Jun 3, 2023

With the upgrade of js-waku to support [email protected] and the introduction of services, we can probably setup some components as services.

Example: ConnectionManager: #1380 (comment)

Needs to be triaged.

@fryorcraken fryorcraken added this to Waku Jun 3, 2023
@danisharora099 danisharora099 moved this to Triage in Waku Jun 3, 2023
@weboko
Copy link
Collaborator

weboko commented Jun 8, 2023

I believe the next step would be to make a PoC and check if it works as intended.

Reference to services - https://github.com/libp2p/js-libp2p/blob/master/doc/migrations/v0.44-v0.45.md#services

@weboko weboko moved this from Triage to To Do in Waku Jun 8, 2023
@weboko weboko added API labels Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: To Do
Development

No branches or pull requests

3 participants