Feature #47858
MyJDownloader API: Keep history of offline devices
| Status: | New | Start date: | 07/16/2014 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  jiaz | % Done: | 0% | |
| Category: | General | |||
| Target version: | - | |||
| Resolution: |
Description
Currently
- call to /my/devicelist: An array of connected devices is returned, e.g.:
{ "list": [ { "id": "efbdea5107ed0300ecb669b1582bf782", "type": "jd", "name": "JDownloader 1" }, { "id": "7bb0c0d9866d2f54f1c1f7f0350f16d8", "type": "jd", "name": "JDownloader 2" } ] } - Calls to offline devices are timing out, creating a long delay on the client side
- Clients can not provide a reason to the user for a device going offline
- Features like adding links to a queue for offline JDownloaders are not possible
- Devices should disconnect from myjd before shutdown of the application and provide a reason for the disconnect
- Include offline devices in the API response for the /listdevices call
- Add a status field for each device, include, if available, a reason why the device went offline (updating, reconnection,...)
- If possible, avoid timing out calls to devices that disconnected