Line 7: |
Line 7: |
| * Real needs of deployments like [[Deployment_Team/Peru/Puno|one-teacher schools in Peru]] and should be as simple as possible; [[Wikipedia:KISS_principle|Keep it simple, wise man!]]; | | * Real needs of deployments like [[Deployment_Team/Peru/Puno|one-teacher schools in Peru]] and should be as simple as possible; [[Wikipedia:KISS_principle|Keep it simple, wise man!]]; |
| * The system, from users point of view, should just work proving high-level services that cover the full collaboration circle that should exist within Sugar learning community; | | * The system, from users point of view, should just work proving high-level services that cover the full collaboration circle that should exist within Sugar learning community; |
− | * It is all about creating high-level services that use regular client-server interaction model with one addition, an optional need to make a synchronization between a distributed server and the main one, the Mothership; In other words, it is all time about having a chain of {{Code|Motherhip <-> [Distributed Server] <-> Client}} interactions; Because: | + | * It is all about creating high-level services that use regular client-server interaction model with one addition, an optional need to make a synchronization between a distributed server and the main one, the Mothership; In other words, it is all time about having a chain of {{Code|Motherhip <-> [Distributed Server] <-> Client}} interactions; |
− | ** Only on the Mothership level, there could be skilled people that can follow not trivial way to solve possible issues;
| |
− | ** Thus, either system should be smart enough to solve issues on its own or it should be as simple as possible delegating not trivial work to the Mothership; The 2nd option is taken;
| |
| | | |
| == Overview == | | == Overview == |
Line 23: |
Line 21: |
| | | |
| In all cases the server API is the same for clients. But depending on connectivity, client might be connected to the Mothership or to an intermediate server. | | In all cases the server API is the same for clients. But depending on connectivity, client might be connected to the Mothership or to an intermediate server. |
− |
| |
− | Todo:
| |
− |
| |
− | :* Would be useful to involve, in automatic manner, clients, i.e., like in case of VCS; client can work with the server or with local replication that needs to be pushed to the server when client will be online.
| |
| | | |
| == Client == | | == Client == |