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

Rewrite peers module - phase one #409

Closed
karmacoma opened this issue Jan 30, 2017 · 3 comments
Closed

Rewrite peers module - phase one #409

karmacoma opened this issue Jan 30, 2017 · 3 comments
Assignees
Milestone

Comments

@karmacoma
Copy link
Member

karmacoma commented Jan 30, 2017

Decoupling @4miners ideas from #406:

Phase 1 of 2: Move peers management to memory instead of database.

@karmacoma
Copy link
Member Author

Move peers management to memory instead of database.

I think we should perform a dump and restore of peers to the database when shutting down and relaunching application. During application run-time we can persist in-memory only.

@karmacoma karmacoma modified the milestones: Core Sprint 01, Core Sprint 02 Jan 30, 2017
@mrv777
Copy link
Contributor

mrv777 commented Feb 7, 2017

Change peers communication protocol from http to websockets

I'm still reading up on websockets and how it works, but curious what you plan to use for it. This one looked interesting if it would be compatible: https://github.com/uWebSockets/uWebSockets

Seems very lightweight and fast

@Isabello
Copy link
Contributor

Isabello commented Feb 7, 2017 via email

@karmacoma karmacoma changed the title Rewrite peers module Rewrite peers module - phase one Feb 22, 2017
karmacoma added a commit that referenced this issue Mar 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants