XS Server Discussion: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
Line 24: Line 24:


Aside from this, much of the long tail video distribution may be best handled by P2P clients directly on the laptops. Discussion ?
Aside from this, much of the long tail video distribution may be best handled by P2P clients directly on the laptops. Discussion ?

=Collaborative/Publishing/Learning Management System=
Moodle could be an option? http://moodle.org

Exchanging published work with other communities could be done using a usb, taking a class ''portfolio'' (using moodle pages) to another village. Distance collaboration can also be done in an asynchronous way, where each school has its page or set of pages in moodle, and it would work like standard mail, travelling by land to another school, kids contributing, commenting, peer-assessing, and then back again.


=Webware=
=Webware=
Line 43: Line 38:


If an alternate definition of "webware" is intended, please expound.
If an alternate definition of "webware" is intended, please expound.

=Repository=
Content centered, but allowing collaboration in building new content. See http://cnx.org for an example. The service is provided as opensource software by the name Rhaptos http://rhaptos.org/. It's Python based.

Revision as of 04:15, 2 February 2007

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

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 separate Instant Messaging service be hosted by the School server?

News

Should the School server support student/teacher/school Blogs?

Should the school server support Forums ?

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 ?

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.