Platform Team/Sugar Network/Architecture: Difference between revisions
No edit summary |
|||
| Line 5: | Line 5: | ||
The technical decisions are tailored by: | The technical decisions are tailored by: | ||
* | * 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; Because: | ||