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

Promoted sign is inefficient redesign to include sign #23

Open
cheme opened this issue Mar 20, 2015 · 1 comment
Open

Promoted sign is inefficient redesign to include sign #23

cheme opened this issue Mar 20, 2015 · 1 comment

Comments

@cheme
Copy link
Owner

cheme commented Mar 20, 2015

On a network level promoted sign of wotstore are a disaster:
when running an accept of wotaccess and querying for promoted sign, subsequent n query reply are send to get actual peersign because promoted sign only return key to the sign.
TODO : Promoted sign should keep being stored with key of peersign only, yet when sent it should resolve and include its peersign.
This could not be achieve easyly with specific keyval serialization, (serialize would require a reference of another kvstore to encode ...), so the best things would be to have a keyval type for storage (the current one) and a keyval type for sending (with peersign included). Both keyval with the same keys obviously.

Plus rewrite promsign function to run as mutable!!!!

@cheme cheme added this to the beta milestone Mar 20, 2015
@cheme
Copy link
Owner Author

cheme commented Nov 22, 2015

Still need redesign (plus usage of striple).

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

1 participant