Jump to content

Platform Team/Sugar Network/Implementation: Difference between revisions

From Sugar Labs
No edit summary
Line 7: Line 7:
* System should support synchronisation between servers and provide full featured text search.
* System should support synchronisation between servers and provide full featured text search.


That's why using [[Platform_team/Active_Document]] to:
That's why using [[Platform_Team/Active_Document|Active Document]] to:


* Server should be as simple/lightweight as possible;
* Server should be as simple/lightweight as possible;
* No SQL, just NoSQL;
* No SQL, just NoSQL;
* Since server should support full featured text search, use Xapian and keep it as a "NoSQL replacement".
* Since server should support full featured text search, use Xapian and keep it as a "NoSQL replacement" with storing data directly in files system;
* The data will be stored in the files system.
* If server will start serving users from the Internet and current implementation won't manage to handle multiple request, another implementation might be created.


== Todo ==
== Todo ==

Revision as of 14:32, 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 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" with storing data directly in files system;
  • If server will start serving users from the Internet and current implementation won't manage to handle multiple request, another implementation might be created.

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.)