School server: Difference between revisions

From OLPC
Jump to navigation Jump to search
m (Reverted edits by RafaelOrtiz (Talk); changed back to last version by Berrybw)
No edit summary
Line 4: Line 4:
When we deploy one laptop per child, we must also provide additional infrastructure extending the capabilities of the laptops. While the laptops are largely self-sufficient, a mesh portal providing connectivity and shared resources greatly extends their utility.
When we deploy one laptop per child, we must also provide additional infrastructure extending the capabilities of the laptops. While the laptops are largely self-sufficient, a mesh portal providing connectivity and shared resources greatly extends their utility.


These persistent services required by OLPC laptops could conceivably be implemented in a fully distributed manner. They are , however, currently provided more economically by a centralized local resource, the school server. The functions provided by this server are [[XS_Server_Discussion|open to debate]], but [[XS_Server_Services|at a minimum they include]] internet communication and storage resources to the school's wireless mesh.
These persistent services required by OLPC laptops could conceivably be implemented in a fully distributed manner. They are , however, currently provided more economically by a centralized local resource, the school server. The functions provided by this server are [[XS_Server_Discussion|open to debate]], but [[XS_Server_Services|at a minimum they include]] internet communication, a centralized presence service and storage resources to the school's wireless mesh.


== Roadmap ==
== Roadmap ==

Revision as of 04:21, 30 March 2008

  This page is monitored by the OLPC team.
  english | 한글 | español HowTo [ID# 121345]  +/-  


When we deploy one laptop per child, we must also provide additional infrastructure extending the capabilities of the laptops. While the laptops are largely self-sufficient, a mesh portal providing connectivity and shared resources greatly extends their utility.

These persistent services required by OLPC laptops could conceivably be implemented in a fully distributed manner. They are , however, currently provided more economically by a centralized local resource, the school server. The functions provided by this server are open to debate, but at a minimum they include internet communication, a centralized presence service and storage resources to the school's wireless mesh.

Roadmap

The school server is in heavy development at the moment (March/April 2008) - following

Technical notes

Meetings


Design Documents

The high-level design of the School server is described here - note that some may be slightly outdated:

See also