I have a web application where users can upload their files read/only to my application. Call this user_file_i.
My application then creates a new file for each file the user uploaded. Call this output_file_i.
My application can asynchronously update the output_file_i.
I love the dropbox user experience, so would like to investigate if I can use dropbox api
as a replacement for my web application file upload. I have not used the dropbox API, so have
no idea if this is a good or bad idea. Would love some guidance.
Some Questions:
Q1: Does the API allow a user of dropbox allow a user to say "share this directory and the files below with application_x" where application_x is my application.
Q2: Does the API allow my application to get notifications when files are added and removed from the above shared folder?
Q3: Does the API allow my application to download the modified file from dropbox where my application is a linux application?
My desire is not to persist the file on my application but rather just down load the file when modified, process it, create an output then forget about the file. So my application is more for a transaction rather then long term storage of the file. My application has many replicas, so do not want to persist locally the user files.
Q4: When my application has created output_file_i, can the API deliver the file to a registered user? Again, without persisting the file in my web application. So if file produced today, my app shares it with user+i and forgets the file, then later the user download the file?
Q5: Since my application is more of a transaction processor, how would my application be billed by dropbox.