prestomation / androidfiledrop Goto Github PK

Currently, AFD only allows a specific user to have one Android device registered on the server. With the growing popularity of Android tablets, it would be ideal if users could, upon uploading a file, specify a device to push to

This would require:

1. Storage of multiple C2DM ids:
   C2DM Device ids are currently stored directly in the User object. A device namespace should probably be created, with each user owning a list of device IDs.
   These device ID's should also be able to be named.
2. Upon uploading, allow the user to specify a device:
   I am imagining the upload page creates a radio button for each device a user owns.
   The desktop uploaders will present the user with similar radio buttons retreived from the server. Possibly a "Refresh" button which will refresh device ids off the server because these will be locally cached.
3. Upon notification, NotifyService will take an id, that id will only be notified if the user owns that id

Download service will not be affected, users can still only store one file at a time.

Currently, everytime a file is uploaded using a desktop uploader, the user must reenter their username and password.
The uploader should ask for auth information rarely.

The first time a desktop uploader is successfully used, the username and authtoken should be securely stored locally. The next time the uploader is ran, the username field should be prepopulated and the password field should be "fake" populated(we are not remembering passwords). If no change is made to either field, the stored username and auth token are used for upload.

The dialog should continue to be shown to allow a user to login as a different user, or, once Issue 1 is accepted, choose which device to use.

Android devices running Android 2.3 or higher use the system Download Manager to download files from the AFD server. These downloads are not secure(i.e. not over https), possibly allowing malicious network neighbors/hops to intercept a file being downloaded.

This is a limitation of the builtin DownloadManager.
This will only be possible if Ice Cream Sandwich(or later) adds this capability, OR the Froyo implementation is augmented with HTTPS support and is used for all Android versions.