-
Notifications
You must be signed in to change notification settings - Fork 89
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
Vectorclock abstraction #370
Conversation
Rewriting the meta data sender module abstract away from dicts
…/antidote into vectorclock_abstraction
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice improvements in code readability 👍
end, ok, SS). | ||
PrintFun = fun(DcId, Time) -> | ||
logger:debug("~w staleness: ~w ms ~n", [DcId, (Now-Time)/1000]) end, | ||
_ = vectorclock:map(PrintFun, SS), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add a vectorclock:foreach
function?
|
||
-module(stable_time_functions). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe add a behavior since these functions are used as callbacks?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's add it once we have more than one instantiation.
Co-Authored-By: Peter Zeller <p_zeller@cs.uni-kl.de>
Co-Authored-By: Peter Zeller <p_zeller@cs.uni-kl.de>
…/antidote into vectorclock_abstraction
Major refactoring of meta_data_sender and related modules to use maps instead of dicts.
Further corrections of the unit tests and simplifications and cleaning up of code.
Hint: Vectorclock dependencies must be adapted still to new vectorclock version with maps.