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

From Sugar Labs
Jump to navigation Jump to search
Line 14: Line 14:
 
** Generate openssl "server.crt" and "server.key".
 
** Generate openssl "server.crt" and "server.key".
 
         <code>cd /etc/ssl/certs/</code>
 
         <code>cd /etc/ssl/certs/</code>
−
<math>sudo openssl req -new -newkey rsa:1024 -days 365 -nodes -x509 -keyout ssl.key -out ssl.crt</math>
+
        <code>sudo openssl req -new -newkey rsa:1024 -days 365 -nodes -x509 -keyout ssl.key -out ssl.crt</code>
 
**  
 
**  
  

Revision as of 07:43, 2 April 2012

Proposal for a client-initiated journal transfer

Workflow

  • The server XO would make available 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.
    • Install package "httpd".
    • Generate openssl "server.crt" and "server.key".
       cd /etc/ssl/certs/
       sudo openssl req -new -newkey rsa:1024 -days 365 -nodes -x509 -keyout ssl.key -out ssl.crt



In a server-initiated operation, the server is responsible for adequate delivery to all the clients, whatever the number may be. In a client-initiated operation, each client is responsible for herself only.


Option Server-Initiated / Client-Initiated Secure Data Transfer Proxy Support Peer to Peer Support (Gabble/Salut)
Looping over "Send To" Server-Initiated Yes/Yes
Sascha's JournalToWebDAV Client-Initiated
Each XO acts as an independent WebDAV server; client uses browser Client-Initiated Yes (HTTPS over SSL) /Yes
Retrieved from "https://wiki.sugarlabs.org/index.php?title=Features/Transfer_to_many_options&oldid=76914"