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
Comments
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. |
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 |
uws is on our list of dependencies to move to ;)
…On Tue, Feb 7, 2017 at 10:41 AM, mrv777 ***@***.***> wrote:
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
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#409 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/APzFsHWhbzv0_sGKTwmxWdz1Nar8o0neks5raJCdgaJpZM4Lxq5z>
.
|
Decoupling @4miners ideas from #406:
Phase 1 of 2: Move peers management to memory instead of database.
The text was updated successfully, but these errors were encountered: