52
edits
Services/DeviceManager: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 39: | Line 39: | ||
* memory usage on mobile device | * memory usage on mobile device | ||
* high availability | * high availability | ||
=== Design ==== | |||
Web app: | |||
* Written using TBD | |||
* Makes calls to REST API when user wants to wipe or find the device's location | |||
Android app == trivial polling mechanism making calls to data exchange server's REST API | |||
Data Exchange Server | |||
* Python app using Django? Bottle? TBD | |||
* REST API consisting of functions for the following: | |||
** WipeDevice(params: device_id): Called by the web app to initiate a device wipe | |||
** GetDeviceStatus(params: device_id): Called by the web app to get a device's coordinates and wiped status | |||
** CheckWipeRequested(params: device_id): Called by the Android app to check if a request has arrived at the server to initiate a wipe | |||
** UpdateWipeStatus(params: device_id, wipe_status): Called by the Android app to let it know that a wipe has succeeded/failed | |||
** UpdateLocation(params: device_id, latitude, longitude): Called by the Android app to notify the server of its latest location | |||
== Second Prototype == | == Second Prototype == | ||
Now we have some basic communication working so | Now we have some basic communication working so handle some of the issues ignored in the first prototype! | ||