Difference between revisions of "Features/Sharing Journal Entries Via School Server"
< Features
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
+ | == Basic Usage == | ||
+ | * This feature helps share Journal/Documents/Mounted-Drives' entries across XOs, via the following two mechanisms | ||
+ | ** Peer-to-Peer mode | ||
+ | *** In this mode, an XO acts as a server, and another XO acts as a client. Thus, each XO has the ability to don the server's hat (when it wishes to allow other | ||
+ | XOs to have its shares); and don the client's hat (when it wishes to access other XOs' shares). | ||
+ | *** Peer-to-Peer sharing 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 | ||
+ | **** XOs connected to the same Access Point (as long as school-server is pingable throughout). | ||
+ | **** XOs connected to the different Access Points (as long as school-server is pingable throughout). | ||
+ | **** Adhoc-Network connections (as long as school-server is pingable throughout). | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | == Example Workflow for Peer-To-Peer Mode == | ||
Revision as of 04:10, 1 September 2012
Basic Usage
- This feature helps share Journal/Documents/Mounted-Drives' entries across XOs, via the following two mechanisms
- Peer-to-Peer mode
- In this mode, an XO acts as a server, and another XO acts as a client. Thus, each XO has the ability to don the server's hat (when it wishes to allow other
- Peer-to-Peer mode
XOs to have its shares); and don the client's hat (when it wishes to access other XOs' shares).
- Peer-to-Peer sharing 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.
- Peer-to-Peer sharing is possible, only when the server and client XO(s) are on the same networks. Thus, peer-to-peer sharing would work on
- 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
- XOs connected to the same Access Point (as long as school-server is pingable throughout).
- XOs connected to the different Access Points (as long as school-server is pingable throughout).
- Adhoc-Network connections (as long as school-server is pingable throughout).
Example Workflow for Peer-To-Peer Mode
SCREENSHOTS
Choose the files to upload to the "School-Server".
Confirmation alert pops up. Choose "Continue"
Enter passphrase for first entry, and choose "Ok". Note that passphrase repeats for uploads are allowed.
After the first entry is uploaded, passphrase needs to be entered for the second entry. Then choose "Ok".
Both uploads finished.
Ensure that "Documents" folder is empty.
Enter a (incorrect) password.
'Passphrase not match' message appears.
Again, choose the entry to copy (download) to Documents.
This time, enter the correct passphrase. The entry is (successfully) downloaded.