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 == |
| | | |
| | | |