Peer manager

[kevaundray]

Having a peer manager would allow each module to call the peer mgr for and not need to deal with the Peers abstract itself. They would just need to know what message they would like to send.

Doing this however will cause an extra layer of dependency. Where moduleX depends on PeerMgr and PeerMgr depends on Peer.

Changing the peer would then cause the Mgr to behave differently, if part of the changed code effects the exposed functionality of Peer. This could in turn cause moduleX to behave differently and or break.

[kevaundray]

The addition of Peer manager would cause a lot of convenience for other modules, the question is therefore how many modules will use it extensively to weigh up the convenience and the dependency problem.

The modules are as follows:

• Sync Manager
• Connection Manager

Even so, connection manager just calls the wrapper which creates a peer. In reality on sync manager extensively uses it. Hence, I think it is better to localise the peer manager if implemented, to only the sync manager. If it does not fit follow the degree of modularity that we want, we can just rip it out.

[kevaundray]

Note: Since it will be a part of sync manager, it will be put till last like sync manager.

[kevaundray]

The dependency could however be de-coupled if we do not embed the peerManager and instead ask for certain functions, like SendMessage() error