Difference between revisions of "Marketing Team/Events/Sugarcamp Boston 2008/Minutes"
Jump to navigation
Jump to search
| Line 43: | Line 43: | ||
* How should the content be delivered to the kid? USB stick? School server? Online library? | * How should the content be delivered to the kid? USB stick? School server? Online library? | ||
| + | |||
| + | * MStone: you can run a web server on the XO! | ||
Revision as of 14:01, 18 November 2008
Presence Scalability
XS scenario
- Search based interface (Morgan Collett)
- Shrink memory footprint (Martin Langoff)
- ODBC ejabberd roaster
- Web based interface for group management
- ejabberd (seems) a convincing implementation (so far)
- ejabberd is very tweakable, configurable, extensible
- Martin working on it, ready in 6-7 weeks?
Global scenario
- Optional feature (privacy, nat, bandwidth...)
- Jabber server buried in remote control panel
- Must restart Sugar to change
eBook reader (Chris Rowe, Bernie, Martin Langoff)
- OLE Nepal asked for an application for opening, reading and browsing PDF books
- OLE Nepal uses a web-based interface to browse for content
- Martin: there are plenty of custom protocols and formats for content librararies
- Martin: the Internet is already a good enough search tool for content
- Chris: 85% of content is PDF, the rest is mostly MSWord
- Chris: OLE Nepal said: "short term, we just want a viewer + some metadata"
- How should the content be delivered to the kid? USB stick? School server? Online library?
- MStone: you can run a web server on the XO!