School server: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
When we deploy one laptop per child, we must also deploy the infrastructure necessary to make |
When we deploy one laptop per child, we must also deploy the infrastructure necessary to make |
||
these laptops useful. The central component of this infrastructure is a school server. The functions provided by this server are open to debate, but at a minimum it provides internet communication and storage resources to the school's wireless mesh. |
these laptops useful. The central component of this infrastructure is a school server. The functions provided by this server are open to debate, but at a minimum it provides internet communication and storage resources to the school's wireless mesh. |
||
A single school server is designed to support between thirty and sixty students. An open area |
|||
of discussion is how these are combined to support larger schools. |
|||
Currently, the School server is described by these documents: |
Currently, the School server is described by these documents: |
||
Revision as of 04:59, 29 January 2007
When we deploy one laptop per child, we must also deploy the infrastructure necessary to make these laptops useful. The central component of this infrastructure is a school server. The functions provided by this server are open to debate, but at a minimum it provides internet communication and storage resources to the school's wireless mesh.
A single school server is designed to support between thirty and sixty students. An open area of discussion is how these are combined to support larger schools.
Currently, the School server is described by these documents:
- Server Specification describes the School Server
- Server Services described the services supported by the School Server
- Server Discussion describes services and enhancements possibly supported by the School Server