34
edits
Changes
no edit summary
#There are three options for the back end:
#There are three options for the back end:
##PHP driven webpage using apache and some sort of SQL
##PHP driven webpage using apache and some sort of SQL
##*<br>+ Using existing server and database technology
##* + Using existing server and database technology
##*<br>+ Doesn't require app, can use browser to get files as well
##* + Doesn't require app, can use browser to get files as well
##*<br>- Requires apache + SQL + PHP support
##* - Requires Apache + SQL + PHP support
##*<br>+ Would be installed if they have Moodle anyways
##* + Would be installed if they have Moodle anyways
##*<br>+ Uses HTTP protocol, easy to implement in client
##* + 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====