XS Server Services: Difference between revisions
(Added Networking) |
No edit summary |
||
Line 43: | Line 43: | ||
==Name Resolution and Service Discovery== |
==Name Resolution and Service Discovery== |
||
The [[School server]] will use and support the use of [[http://en.wikipedia.org/wiki/Zeroconf|Zeroconf]] techniques for device name declaration and service discovery. |
The [[School server]] will use and support the use of [[http://en.wikipedia.org/wiki/Zeroconf |Zeroconf]] techniques for device name declaration and service discovery. |
||
Should it also support traditional DNS (exporting the mDNS names)? |
Should it also support traditional DNS (exporting the mDNS names)? |
Revision as of 07:09, 28 January 2007
These are services that the School server will provide. Additional services under consideration for deployment are listed separately.
Please help by adding links to existing pages discussing these topics, if you are aware of them
Library
Are any books (digital documents) downloaded to the laptops, or is most content accessed from the school server?
Caching
How much of the library is local and how much is simply a cache of a larger regional/country library ? Can a transparent HTTP cache applied to a centralized library server provide the desired user experience (quick access to common books and access to a large catalog of books)?
Traditional Media
What is mechanism for user submissions of traditional (static) media to the library? The centralized library will probably have a human-filtered request mechanism. What about the local library? Will teachers (and students) have a place to put resources they create where all can retrieve?
Collaborative and Dynamic Media
What about local wikis? Should they be supported on the School server? To some extent, a Wiki may be used as the means for uploading and cataloging static media local to the school library.
Backup
What are the plans for providing additional storage to users of the XO laptops? Is this a backup (sync) or just storage for content `overflowed' from the laptops ? Should the school provide automatic backup of the laptop contents ?
Network Router
The School server is first and foremost a node in the wireless mesh which provides connectivity to the larger internet.
A starting assumption is that it is largely a transparent router. It does not perform any network address translation, and very little packet filtering. It will perform bandwidth shaping to ensure fair access to the internet.
HTTP Caching
The only packet filtering proposed is a transparent proxy on port 80, which will allow a caching of commonly accessed HTTP (web) content to occur locally. This will reduce the load on the internet connection, as well as the response time seen by a user.
Name Resolution and Service Discovery
The School server will use and support the use of [|Zeroconf] techniques for device name declaration and service discovery.
Should it also support traditional DNS (exporting the mDNS names)?