Difference between revisions of "Platform Team/Sugar Network/Implementation"

From Sugar Labs
Jump to navigation Jump to search
Line 1: Line 1:
 +
== Summary ==
 +
 +
The requirements:
 +
 +
* Implement initial system in [[Platform_Team/Sugar_Network/0.1/Roadmap|short period of time]];
 +
* Server should work on XO laptops;
 +
* System should support synchronisation between servers and provide full featured text search.
 +
 +
That's why using [[Platform_team/Active_Document]] to:
 +
 +
* Server should be as simple/lightweight as possible;
 +
* No SQL, just NoSQL;
 +
* Since server should support full featured text search, use Xapian and keep it as a "NoSQL replacement".
 +
* The data will be stored in the files system.
 +
 
== Todo ==
 
== Todo ==
  
 
* Network notifications framework to, e.g., let client cache resources and refetch them only on updates. Reuse existing or implement something similar to Facebook's [http://developers.facebook.com/docs/reference/api/realtime/ real-time updates].
 
* Network notifications framework to, e.g., let client cache resources and refetch them only on updates. Reuse existing or implement something similar to Facebook's [http://developers.facebook.com/docs/reference/api/realtime/ real-time updates].
 +
* Support collaborative work on Wiki pages for different resources.
 +
 +
== Getting involved ==
 +
 +
{{:Sugar_Network/Feedback}}

Revision as of 14:30, 19 December 2011

Summary

The requirements:

  • Implement initial system in short period of time;
  • Server should work on XO laptops;
  • System should support synchronisation between servers and provide full featured text search.

That's why using Platform_team/Active_Document to:

  • Server should be as simple/lightweight as possible;
  • No SQL, just NoSQL;
  • Since server should support full featured text search, use Xapian and keep it as a "NoSQL replacement".
  • The data will be stored in the files system.

Todo

  • Network notifications framework to, e.g., let client cache resources and refetch them only on updates. Reuse existing or implement something similar to Facebook's real-time updates.
  • Support collaborative work on Wiki pages for different resources.

Getting involved

  • Submit your bug report or feature request.
  • Browse our implementation discussions, and post your feedback. (You should join this discussion list in order to avoid having your messages postponed for moderation.)