34
edits
Changes
Jump to navigation
Jump to search
Line 60:
Line 60: − **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. + − **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.+
no edit summary
*We initially tried to set up an nfs mount however, this did not work.
*We initially tried to set up an nfs mount however, this did not work.
*The file distribution system will be in two parts:
*The file distribution system will be in two parts:
#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.
***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
***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