Difference between revisions of "Features/Transfer to many options"

Latest revision as of 12:26, 26 March 2013

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 mode
  - 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).

Credits

Plan Ceibal
- For supporting this feature development.

Sascha Silbe silbe@activitycentral.com
- Initial Proposal for the solution based on WebDAV.

Anish Mangal anish@activitycentral.com
- Showed why simply accessing the webdav shares via "Browse" activity won't work.
- The reason is that accessing Sugar-WebDAV shares via "Browse" (or in any browser), would show only the availability of files. But a Sugar-entry is more than just the (data) file; it is a combination of
  - Metadata-file
  - Data-file
  - Preview-file (optional)
- Also, the current workflow conforms to the sugar look-and-feel too. (Thanks again Anish).

Ruben Rodriguez ruben@activitycentral.com
- Feedback on the "peer-to-peer" mechanism; now when the user clicks "Access Share", the user is directly taken to the newly mounted remote-share view.

Nitika Mangal nitika@activitycentral.com
- Testing

David Rodriguez daroal@activitycentral.com
- Testing

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.

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

[PEER 1] Initial "Local Shares" View

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

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

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

[PEER 2] Initial "Journal" - View.

[PEER 2] Neighborhood View.

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

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

[PEER 2] Copy the entry to the journal.

[PEER 2] Final "Journal" View.

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

Example Workflow for Via-School-Server Mode

NOTES

- An entry present in "School Server Shares", is available to all the XOs. There isn't any mounting or anything required as such.
- Note that the entries present in "School Server Shares", have nothing to do with the entries present in "Local Shares".
- In the following screenshots' example, an XO uploads an entry to the school-server, and then downloads the same. HOWEVER, NOTE THAT ANY XO WOULD BE ABLE TO DOWNLOAD THE ENTRY PRESENT ON THE SCHOOL-SERVER, AND NOT ONLY NECESSARILY THE UPLOADER.

SCREENSHOTS

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

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

[UPLOAD] Enter the pasphrase when prompted.

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

[DOWNLOAD] Initial "Documents" view.

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

[DOWNLOAD] Enter (incorrect) password.

[DOWNLOAD] 'Passphrase not match' error occurs.

[DOWNLOAD] Try copying again.

[DOWNLOAD] Enter (correct) password.

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

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

TEST-CASES THAT NEED TO PASS

Inter-copying an entry between Journal/Documents/Mounted-Drives/Local-Shares/School-Server-Shares should behave in the same way. For eg, in the peer-to-peer mode, it was shown that the source-entry (on PEER-1) had a preview; the same was true when the entry finally arrived on PEER-2. In particular, the preview should "go along" as and when the entry goes, intra-XO or inter-XO.

Things should work fine, irrespective of the fact that whether the sharing is done via single-mode, or batch-mode.

Difference between revisions of "Features/Transfer to many options"

Latest revision as of 12:26, 26 March 2013

Contents

Basic Usage

Credits

Example Workflow for Peer-To-Peer Mode

NOTES

SCREENSHOTS

[PEER 1] "Journal" - View.

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

[PEER 1] Initial "Local Shares" View

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

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

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

[PEER 2] Initial "Journal" - View.

[PEER 2] Neighborhood View.

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

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

[PEER 2] Copy the entry to the journal.

[PEER 2] Final "Journal" View.

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

Example Workflow for Via-School-Server Mode

NOTES

SCREENSHOTS

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

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

[UPLOAD] Enter the pasphrase when prompted.

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

[DOWNLOAD] Initial "Documents" view.

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

[DOWNLOAD] Enter (incorrect) password.

[DOWNLOAD] 'Passphrase not match' error occurs.

[DOWNLOAD] Try copying again.

[DOWNLOAD] Enter (correct) password.

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

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

TEST-CASES THAT NEED TO PASS

Navigation menu

Search

@@ Line 1: / Line 1: @@
-=== Proposal for a client-initiated journal transfer (1-to-N feature) ===
+__TOC__
+<br style="clear: both" />
+== Basic Usage ==
-== Workflow ==
+* This feature helps share Journal/Documents/Mounted-Drives' entries across XOs, via the following two mechanisms ::
-* The server XO would make its shares available via WebDAV, running in the context of "httpd" service.
-* The client XO would connect to the server XO via its browser.
-* Therafter, "Browse" would take over.
-== Details ==
-* '''Setting up WebDAV on a server XO.'''
+**Peer-to-Peer mode
-** Install package "httpd".
+*** 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
-** Generate openssl "server.crt" and "server.key".
+**** XOs connected to the same Access Point.
-        <code>cd /etc/ssl/certs/</code>
+**** Adhoc-Network connections.
-        <code>sudo openssl req -new -newkey rsa:1024 -days 365 -nodes -x509 -keyout ssl.key -out ssl.crt</code>
-** Configure "/etc/httpd/conf.d/ssl.conf" to setup the WebDAV share. Sample file : [[media:ssl.conf]]
-*** Firstly, this sets up the paths "SSLCertificateFile" and "SSLCertificateKeyFile", which are required for HTTPS over SSL.
-*** Secondly, sets up "/var/www/web1/web" as the "webdav" folder. In other words, whetever entries are present in this folder, will be made available for the client XOs.
-** Generate authentication file for the webdav folder. These user-password credentials will be asked whenever a client tries to access the webdav folder. For example, the following list of commands sets "test" as the user, and "olpc" as the password.
-        <code>sudo htpasswd -c /var/www/web1/passwd.dav test
-        New password:  <olpc>
-        Re-type new password:  <olpc>
-        Adding password for user test</code>
-** Start service "httd".
-** ALL THESE STEPS WOULD BE DONE AS PART OF OOB STAGE.
-* '''[User-Workflow] Exporting Data to WebDav, on a server XO.'''
-** Sascha's JournalToWebDAV workflow.
-*** step 1
-*** step 2
-*** step 3
-*** step 4
-** Alternatively,
-*** Add "Share" listview in the bottom panel-tray; that would make a total of 4 types of listview - Journal, Documents, Mounted-Drives, Share.
-*** "Share" would follow all the schematics of "Documents" type. After all, "Share" is just a folder in the filesystem (like "Documents").
-*** The corresponding folder is "/var/www/web1/web" (as configured in "/etc/httpd/conf.d/ssl.conf").
-*** All entries in the "Share" folder would be available to client XOs.
+**Via-School-Server mode
+*** 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).
-* '''[Code-Requirements] Exporting Data to WebDav, on a server XO.'''
-** Sascha has already coded the first alternative.
-** For the second alternative, "Share" listview needs to be added on the lines of "Documents" listview. Code-reuse should be done as much as possible. Ideally, there should just be a difference of the "folder-path".
-* '''[User-Workflow] Client XO wishes to access the share of Server XO.'''
-** Navigates to the "Neighborhood" view.
-** Hovers over the "Server" buddy.
-** The popup appears, which has a new entry "Access Share" (in addition to "Make Friend").
-** Clicks on "Access Share".
-** The "Browser" activity opens, with the url pointing to the "Server" buddy's webdav share.
-** Thereafter, client may navigate the webdav directory hierarchy, or download files (all of which is already built in the "Browse" activity). Most importantly, there is the "Keep Link" feature in "Browse", which nicely downloads the webdav-entry, and promptly saves it in the "Journal" - something that happens in the "Send To" feature as well.
-* '''[Code-Requirements] Client XO wishes to access the share of Server XO.'''
-** Mapping a neighborhood-buddy to its IP Address
-*** Luckily, in the method "def __buddy_updated_cb(self, account, contact_id, properties):" in "jarabe/model/neighborhood.py", there is the "properties['ip4-address']", which contains the IP address of the buddy. All that is needed is to persist it in the "BaseBuddyModel" in "jarabe/model/buddy.py".
-*** When the client clicks on "Access Share" on the buddy, this IP Address can be easily retreived, and the URI formed "https://<IP Address>/webdav"
-** Opening up the server's webdav
-*** The generated URI would be passed to the "Browse" activity; and thereafter, "Browse" would take over.
-** A minor query, regarding the last point, has been posted at http://lists.sugarlabs.org/archive/sugar-devel/2012-April/036425.html. (For resolving this, some additional code may have to be written, but that is something perfectly doable. However, currently awaiting a reply, to see if the code for this already exists :-) ).
-== [ARCHIVE] Possible options ==
+== Credits ==
+* '''Plan Ceibal'''
+** For supporting this feature development.
-In a server-initiated operation, the server is responsible for adequate delivery to all the clients, whatever the number may be.
+* '''Sascha Silbe''' ''silbe@activitycentral.com''
-In a client-initiated operation, each client is responsible for herself only.
+** Initial Proposal for the solution based on WebDAV.
-{| class="wikitable"
+* '''Anish Mangal''' ''anish@activitycentral.com''
-|-
+** Showed why simply accessing the webdav shares via "Browse" activity won't work.
-! Option
+** The reason is that accessing Sugar-WebDAV shares via "Browse" (or in any browser), would show only the availability of files. But a Sugar-entry is more than just the (data) file; it is a combination of
-! Server-Initiated / Client-Initiated
+*** Metadata-file
-! Secure Data Transfer
+*** Data-file
-! Proxy Support
+*** Preview-file (optional)
-! Peer to Peer Support (Gabble/Salut)
+** Also, the current workflow conforms to the sugar look-and-feel too. (Thanks again Anish).
-|-
-| Looping over "Send To"
-| Server-Initiated
+* '''Ruben Rodriguez''' ''ruben@activitycentral.com''
-|
+** Feedback on the "peer-to-peer" mechanism; now when the user clicks "Access Share", the user is directly taken to the newly mounted remote-share view.
-|
-| Yes/Yes
-|-
+* '''Nitika Mangal''' ''nitika@activitycentral.com''
-| Sascha's JournalToWebDAV
+** Testing
-| Client-Initiated
-|
-|
+* '''David Rodriguez''' ''daroal@activitycentral.com''
-|
+** Testing
-|-
-| Each XO acts as an independent WebDAV server; client uses browser
+== Example Workflow for Peer-To-Peer Mode ==
-| Client-Initiated
-| Yes (HTTPS over SSL)
-|
+== NOTES ==
-| /Yes
+** 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. ==
+:[[File:p11.png|640px]]
+== [PEER 1] Detail view of the journal-entry. Note the preview presence. ==
+:[[File:p12.png|640px]]
+== [PEER 1] Initial "Local Shares" View ==
+:[[File:p13.png|640px]]
+== [PEER 1] Copy the journal entry to "Local Shares", to make it available for sharing to other peers. ==
+:[[File:p14.png|640px]]
+== [PEER 1] "Local Shares" view, after copying the entry. ==
+:[[File:p15.png|640px]]
+== [PEER 1] The detail view in "Local Shares". NOTE that the preview MUST be present, and it must be same as that of "Journal". ==
+:[[File:p16.png|640px]]
+== [PEER 2] Initial "Journal" - View. ==
+:[[File:p20.png|640px]]
+== [PEER 2] Neighborhood View. ==
+:[[File:p21.png|640px]]
+== [PEER 2] Click on "Access Share" of the peer, whose shares need to be accessed. ==
+:[[File:p22.png|640px]]
+== [PEER 2] The peer's shares are mounted. ==
+:[[File:p23.png|640px]]
+== [PEER 2] Copy the entry to the journal. ==
+:[[File:p24.png|640px]]
+== [PEER 2] Final "Journal" View. ==
+:[[File:p25.png|640px]]
+== [PEER 2] Detail-view of the entry. Note that the preview is the same as was on the remote peer. ==
+:[[File:p26.png|640px]]
+== Example Workflow for Via-School-Server Mode ==
+== NOTES ==
+** An entry present in "School Server Shares", is available to all the XOs. There isn't any mounting or anything required as such.
+** Note that the entries present in "School Server Shares", have nothing to do with the entries present in "Local Shares".
+** In the following screenshots' example, an XO uploads an entry to the school-server, and then downloads the same. HOWEVER, NOTE THAT ANY XO WOULD BE ABLE TO DOWNLOAD THE ENTRY PRESENT ON THE SCHOOL-SERVER, AND NOT ONLY NECESSARILY THE UPLOADER.
+== SCREENSHOTS ==
+== [UPLOAD] Initially, no entries are present on the school-server. ==
+:[[File:sss1.png|640px]]
+== [UPLOAD] Choose an entry to upload to the school-server. ==
+:[[File:sss2.png|640px]]
+== [UPLOAD] Enter the pasphrase when prompted. ==
+:[[File:sss3.png|640px]]
+== [UPLOAD] After uploading, ensure that the entry has in fact been uploaded to the school-server. ==
+:[[File:sss4.png|640px]]
+== [DOWNLOAD] Initial "Documents" view. ==
+:[[File:sss5.png|640px]]
+== [DOWNLOAD] Choose to copy the entry from school-server, to "Documents". ==
+:[[File:sss6.png|640px]]
+== [DOWNLOAD] Enter (incorrect) password. ==
+:[[File:sss7.png|640px]]
+== [DOWNLOAD] 'Passphrase not match' error occurs. ==
+:[[File:sss8.png|640px]]
+== [DOWNLOAD] Try copying again. ==
+:[[File:sss9.png|640px]]
+== [DOWNLOAD] Enter (correct) password. ==
+:[[File:sss10.png|640px]]
+== [DOWNLOAD] Confirm that the entry has been successfully downloaded. ==
+:[[File:sss11.png|640px]]
+== [DOWNLOAD] Ensure that in the detail view, the uploader-details are present. ==
+:[[File:sss12.png|640px]]
+== TEST-CASES THAT NEED TO PASS ==
+* Inter-copying an entry between Journal/Documents/Mounted-Drives/Local-Shares/School-Server-Shares should behave in the same way. For eg, in the peer-to-peer mode, it was shown that the source-entry (on PEER-1) had a preview; the same was true when the entry finally arrived on PEER-2. In particular, the preview should "go along" as and when the entry goes, '''intra-XO''' or '''inter-XO'''.
+* Things should work fine, irrespective of the fact that whether the sharing is done via single-mode, or batch-mode.