| Line 56: |
Line 56: |
| | | | |
| | In the end, we want to have instructions and some supporting scripts to modify the standard OLPC School Server to support a reading library and our campus environment as independent features. | | In the end, we want to have instructions and some supporting scripts to modify the standard OLPC School Server to support a reading library and our campus environment as independent features. |
| − | ====File Distribution System==== | + | ====[[School_Server/RIT/File_Distribution_System|File Distribution System]]==== |
| − | An alternative to extending e-book readers - a file distribution system for the server and a client for the XO. | + | An alternative to extending e-book readers - a file distribution system for the server and a client for the XO. |
| − | #We initially tried to set up an nfs mount however, this did not work.
| + | |
| − | #The file distribution system will be in two parts:
| + | See the [[School_Server/RIT/File_Distribution_System|Project Page]]. |
| − | ##Some server code that will keep a database of files and metadata about each file; the server will be viewed from a standard web browser as well as have an api that will allow our client to download files over HTTP.
| |
| − | ##*Some optional features could be to allow each person to have a public file store that others can browse.
| |
| − | ##The client side will be written in python; this app will ask the server for the file list and metadata, which will allows users to browse the files and any file they want they can click on and download - the downloaded file will show up in their journal.
| |
| − | ##*This app would allow them to search for files or browse them in a more organized wat than the journal system and they will be able to download the files they want
| |
| − | #The front end would be a simple python activity for the XO
| |
| − | #There are three options for the back end:
| |
| − | ##PHP driven webpage using apache and some sort of SQL
| |
| − | ##* + Using existing server and database technology
| |
| − | ##* + Doesn't require app, can use browser to get files as well
| |
| − | ##* - Requires Apache + SQL + PHP support
| |
| − | ##* + Would be installed if they have Moodle anyways
| |
| − | ##* + Uses HTTP protocol, easy to implement in client
| |
| − | ##Python server application
| |
| − | ##* - We would have to implement our own server (and protocol if we do not use HTTP)
| |
| − | ##* - Could potentially not have a website style interface
| |
| − | ##* + Does not require Apache
| |
| − | ##* - Always running on server even when not in use
| |
| − | ##FTP System
| |
| − | ##* - This would be the least desirable system as it would not support metadata
| |
| − | #We believe a file distribution system will be more valuable to the community as it could be used to distribute activities (the distribute client can be downloaded with the browse activity from its web-front end and then they can use the downloaded activity)
| |
| − | #It can also be used to download e-books from a PDF system
| |
| − | #The client could also make a file wish list so the next time they are online it automatically downloads the requested files; or the teacher can mark a file to be automatically downloaded
| |
| | | | |
| | ===Necessary Tasks=== | | ===Necessary Tasks=== |