Refactor old routing naming and modules - replace peer with node

Description

The intention now is that "node" represents a non-client Routing instance, and "peer" represents any Routing instance, client or node. Generally the code will need most instances of peer replaced with node. Exceptions where "peer" is still appropriate are:

  • peer_manager:eerManager

  • peer_manager:eerState

  • peer_manager:eerInfo

  • src/mock_crust::* (not tests/mock_crust::* though)

  • states::common::base::handle_lost_peer() (and types implementing this trait)

  • any comments using the term "peer-to-peer"

Environment

None

Assignee

Nikita Baksalyar

Reporter

Nikita Baksalyar

Labels

Start date

2018/02/01

End date

2018/02/14

Task progress

None

Baseline start date

None

Baseline end date

None

Story Points

8

Components

Priority

Major
Configure