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

1394, 1395, 1397, 1398 and other fixes #1400

merged 10 commits into from Mar 20, 2017


None yet
5 participants

afck commented Mar 20, 2017

No description provided.

Fraser999 and others added some commits Mar 16, 2017

feat/node: cache changed section prefixes
This implements a cache of prefixes which is populated while a merge is ongoing and is drained
when the merge completes.  The prefixes represent other sections whose prefixes have changed while
the merge was ongoing.  Once the merge is complete, a SectionUpdateRequest is sent to each changed
feat/node: add a cache for merge messages
Only call the routing table merge methods once the messages from both
sides have accumulated. This also fixes out-of-sequence merge messages
if several merges occur in quick succession.
feat/bootstrapper-kind: keep hold of the bootstrapper kind
This will help us verify that someone who bootstrapped as client-kind does not send client_restriction as false later in ClientIdentify
fix/node: limit section update split and sec update request cache
Only split if needed when recd sec update prefix is not compatible with self.our_prefix
Do not cache prefix for sec update request if recd prefix is self.our_prefix().sibling()

This comment has been minimized.

Show comment
Hide comment

maidsafe-highfive Mar 20, 2017

@afck: no appropriate reviewer found, use r? to override

maidsafe-highfive commented Mar 20, 2017

@afck: no appropriate reviewer found, use r? to override

@Viv-Rajkumar Viv-Rajkumar merged commit 52babb7 into maidsafe:master Mar 20, 2017

2 checks passed

continuous-integration/appveyor/pr AppVeyor build succeeded
continuous-integration/travis-ci/pr The Travis CI build passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment