= !BluePrint: Mobile Client Peer-to-Peer Synchronization =
[[TOC]]

== Introduction ==
Peer-to-peer sync will enable [http://eden.sahanafoundation.org/wiki/DeveloperGuidelines/EdenMobile EdenMobile] users to synchronize data between their devices without connecting to a server. This will allow mobile users to operate and collaborate more easily in areas where internet access is unreliable or unavailable.

Peer-to-peer sync capabilities exist in [http://developer.servalproject.org/dokuwiki/doku.php?id=content:servalmesh:main_page Serval Mesh] and a number of messaging apps including [https://briarproject.org/ Briar], [https://github.com/casific/murmur Murmur] and [http://whispercomm.org/shout/ Anonymouse].
== Stakeholders ==
!EdenMobile users are the primary stakeholders - they will be able to use P2P sync to share data with each other. The data subjects will also be stakeholders, and appropriate data handling controls to protect the confidentiality, integrity and authenticity of data must be built in. If the server needs to be aware of P2P sync, for example in order to deduplicate data received from mobile clients, then the people deploying and operating the server will also be stakeholders.
== User Stories ==
[https://code.briarproject.org/akwizgran/briar/uploads/655c21456bbc36a83193bdb5e0473f07/SahanaEDENBrambleProjectUseCases.odt User stories]
== Requirements ==
=== Functional ===
=== Non-functional ===
http://en.wikipedia.org/wiki/Non-functional_requirements
=== Interoperability ===
=== Standards ===
=== System Constraints ===

== Design ==
<Where relevant include alternative design options>
=== Data Model ===
(e.g. EER or class diagrams)
=== Workflows ===
<Diagrams or Pseudocode> 
=== Site Map ===
<for User Interface solutions>
=== Wireframes ===
<for User Interface solutions>
=== Technologies ===

== Current Implementation ==
<Leave open for a list of existing implementation of this solution in Sahana Eden:>
<*a brief description of the implementation (date/time, name, design options chosen)>
<*a link to the code>
<*list of deployments of the implementation>
<*links to case studies>
<*short analysis of achievements/problems>

== Planned Implementation ==
<List of goals for your implementations which you (include your name/github repo/IRC handle) are currently working on>

== Future Extensions ==
<List of features which could be included, but are outside of the scope of this extension>

== Outstanding Questions ==
<Questions about the features or design that haven't been (and need to be) answered>

== References ==
<Links to external resources>

----
BluePrint