Features/Transfer to many options

From Sugar Labs
Jump to navigation Jump to search

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

  • The server XO would make available its shares available via WebDAV, running in the context of "httpd" service.
    • first point
    • second point



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