Changes between Version 12 and Version 13 of BluePrint/Mobile/P2PSync


Ignore:
Timestamp:
05/30/17 15:19:04 (7 years ago)
Author:
MichaelRogers
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Mobile/P2PSync

    v12 v13  
    2929
    3030===== 1.4. Peer authentication =====
    31 When the user has chosen a device to peer with, the P2P sync component '''must''' allow the user to authenticate the peer before granting the peer access to any data. The P2P sync component '''may''' allow the user to continue without authenticating the peer.
     31When the user has chosen a device to peer with, the P2P sync component '''must''' allow the user to authenticate the peer before giving the peer access to any data. The P2P sync component '''may''' allow the user to continue without authenticating the peer.
    3232
    3333===== 1.5. Peer persistence =====
     
    4242
    4343===== 3.1. Data selection =====
    44 The P2P sync component '''may''' allow the user to choose which data to synchronize, either with peers in general or with each specific peer. When data is received from a peer, the P2P sync component '''may''' automatically choose it for synchronization with other peers.
     44The P2P sync component '''may''' allow the user to choose which data to synchronize. When data is received from a peer, the P2P sync component '''may''' automatically choose it for synchronization with other peers.
    4545
    4646===== 3.2. Data deletion =====
     
    8181
    8282=== Interoperability ===
    83 For a given deployment, the same version of the !EdenMobile app will be used for all mobile devices, which should minimize interoperability issues. The protocols used between peers, and between mobile devices and the destination server, should use version negotiation so that any interoperability issues are detected as early as possible. Interoperability with other applications is not required.
     83For a given deployment, the same version of the !EdenMobile app will be installed on all mobile devices, which should minimize interoperability issues. The protocols used between peers, and between mobile devices and the destination server, should use version negotiation so that any interoperability issues are detected as early as possible. Interoperability with other applications is not required.
    8484
    8585=== Standards ===