Difference between revisions of "Features/Sharing Journal Entries Via School Server"

From Sugar Labs
Jump to navigation Jump to search
Line 27: Line 27:
  
  
== TERMINOLOGIES ==
+
== NOTES ==
*'''Local Shares'''
 
 
** An entry present in "Local Shares", is available to other peers, when the peer(s) mount this XO's shares.
 
** An entry present in "Local Shares", is available to other peers, when the peer(s) mount this XO's shares.
 
** Note that the entries present in "Local Shares", have nothing to do with the entries present in "School Server Shares".
 
** Note that the entries present in "Local Shares", have nothing to do with the entries present in "School Server Shares".
 
+
** In the following screenshots' example, "PEER 2" mounts the shares of "PEER 1"; and uses that to copy entries onto its own XO. Thus, the entry is copied from XO-of-PEER-1 to XO-of-PEER-2.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  
  

Revision as of 02:17, 4 September 2012

Basic Usage

  • This feature helps share Journal/Documents/Mounted-Drives' entries across XOs, via the following two mechanisms ::


    • Peer-to-Peer mode
      • Sharing in this mode is possible, only when the server and client XO(s) are on the same networks. Thus, peer-to-peer sharing would work on
        • XOs connected to the same Access Point.
        • Adhoc-Network connections.


    • Via School-Server
      • In this mode, an XO uploads an entry to the central School Server; from where the client XO(s) may download the entry.
      • This mode of sharing works as long as the School-Server is HTTP-pingable between the server and client XOs. Thus, this mode of sharing would work when
        • XOs are connected to the same Access Point (as long as school-server is pingable throughout).
        • XOs are connected to the different Access Points (as long as school-server is pingable throughout).
        • XOs are conencted to Adhoc-Network (as long as school-server is pingable throughout).




Example Workflow for Peer-To-Peer Mode

NOTES

    • An entry present in "Local Shares", is available to other peers, when the peer(s) mount this XO's shares.
    • Note that the entries present in "Local Shares", have nothing to do with the entries present in "School Server Shares".
    • In the following screenshots' example, "PEER 2" mounts the shares of "PEER 1"; and uses that to copy entries onto its own XO. Thus, the entry is copied from XO-of-PEER-1 to XO-of-PEER-2.



SCREENSHOTS

[PEER 1] "Journal" - View.

P11.png






[PEER 1] Detail view of the journal-entry. Note the preview presence.

P12.png






[PEER 1] Initial "Local Shares" View

P13.png






[PEER 1] Copy the journal entry to "Local Shares", to make it available for sharing to other peers.

P14.png






[PEER 1] "Local Shares" view, after copying the entry.

P15.png







[PEER 1] The detail view in "Local Shares". NOTE that the preview MUST be present, and it must be same as that of "Journal".

P16.png








[PEER 2] Initial "Journal" - View.

P20.png






[PEER 2] Neighborhood View.

P21.png






[PEER 2] Click on "Access Share" of the peer, whose shares need to be accessed.

P22.png






[PEER 2] The peer's shares are mounted.

P23.png






[PEER 2] Copy the entry to the journal.

P24.png







[PEER 2] Final "Journal" View.

P25.png






[PEER 2] Detail-view of the entry. Note that the preview is the same as was on the remote peer.

P26.png






[UPLOAD] Initially, no entries are present on the school-server.

Sss1.png




[UPLOAD] Choose an entry to upload to the school-server.

Sss2.png




[UPLOAD] Enter the pasphrase when prompted.

Sss3.png




[UPLOAD] After uploading, ensure that the entry has in fact been uploaded to the school-server.

Sss4.png




[DOWNLOAD] Initial "Documents" view.

Sss5.png




[DOWNLOAD] Choose to copy the entry from school-server, to "Documents".

Sss6.png





[DOWNLOAD] Enter (incorrect) password.

Sss7.png




[DOWNLOAD] 'Passphrase not match' error occurs.

Sss8.png




[DOWNLOAD] Try copying again.

Sss9.png




[DOWNLOAD] Enter (correct) password.

Sss10.png




[DOWNLOAD] Confirm that the entry has been successfully downloaded.

Sss11.png




[DOWNLOAD] Ensure that in the detail view, the uploader-details are present.

Sss12.png