XS Server Discussion
These are services which the School server might provide. Services already deemed essential are listed separately.
Please help by adding links to existing pages discussing these topics, if you are aware of them
Video
While static video objects, such as movies and short clips, may be stored and accessed using the Library service, local distribution of live video requires a dedicated service.
Aside from this, much of the long tail video distribution may be best handled by P2P clients directly on the laptops. Discussion ?
- Video serving can be done by file serving over efficient protocols. HTTP suffices and can be cached and randomly accessed. NFS, ATA over Ethernet, VOIP, MMS, Multicast are all available to gain even more speed. We must prepare for the laptops to transmit continuous AV-streams of how they experience their environment and their data must be intelligently compressed to store them for historical research like where did I last have my keyring?
Global Positioning
It has been suggested that the school servers include a GPS receiver, in order to provide them with accurate location and time information. This would then be available as a web service for access by other applications.
The main advantage of including GPS on the server is that it provides the server with its precise location automatically. As the school servers are expected to remain in a relatively fixed location (within the school building, or up to 100m), their location could be provided at install time.
- The country, school, and students would know where the servers actually are --- not where they are claimed to be. By extension, you would know more about the location of the laptops that are seen by the server.
- You would have a great source of time.
- Server location would be an additional theft deterrent
Possible disadvantages of including GPS on the server are:
- Cost
- How expensive is a GPS locator? Can't you plug one on USB? Wouldn't it be more helpful in the laptops? Aren't we waiting for a Galileo locator?
- Inability to work indoors (especially with tin roof!)
- Isn't the tin roof a problem for the uplink and the mesh as well, meaning there will need to be some sort of antenna cluster & harness already?
- True. The WiFi access points connect to the servers via 2-5m USB cables. Still, the mesh will spread out through side walls better than the GPS will go up.
SIP Directory
A SIP directory should be provided for XO laptop owners. This doesn't have to be implemented locally on the School server, although the same management interface used for security on the laptops might be a convenient place to manage this directory as well.
Instant Messaging
Should a Instant Messaging service (separate from SIP) be hosted by the School server?
- Yes, the best currently available IM is Skype, I am a Skype shareholder and plan to have the shareholders conference vote for open-sourcing the Skype protocol and source code so it can be debugged and brought closer to perfection.
- Since the Jabber (XMPP) protocol provides IM functionality (e.g. XO Chat, Google Talk) there seems to be little or no point in providing yet another service, especially since XMPP is designed to support gatewaying to other IM services (although it's not clear if this has ever been implemented, nor if ejabberd would support this in any way). --@alex 12:42, 27 February 2008 (EST)
News
Should the School server support student/teacher/school Blogs?
- Yes, every student who has a gmail account should be able to log in and webmaster a virtual host.
Should the school server support Forums ?
- Yes, but no unstandardized PHP crap but the good old ones: a relaying SMTP server with a self-service GNU mailman list server with NNTP archive access and eternal storage (we have enough disk space to save all messages finally) and NNTP proxying to all Usenet groups.
Webware
- It can also work as a webware provider, extending the software offer in each laptop.
Webware as in browser-based applications which are either in Java or ECMAscript (nee Javascript) ? Or webware as in applications like [Moodle], which have a back-end component which would run on the School server as well as browser-based component ?
In the case of the former, the Library should be sufficient --- the line between application and media content is blurring.
In the case of the latter (i.e. those with a component executing on the server), the infrastructure for installing, configuring, managing, and updating user-provided services on the School server should be similar (identical ?) to that used for OLPC-provided services. Perhaps a portion of the Library should be designated for user contributed software, which includes server "modules" as well as laptop "modules" ?
If an alternate definition of "webware" is intended, please expound.
Opportunistic File Distribution
As the XS_Server is providing a central point for OLPC devices and other mobile devices, why not providing an opportunistic file distribution? just like [Forban]