Skip to content
This repository has been archived by the owner on Dec 26, 2022. It is now read-only.

Implement request status polling #740

Open
howjmay opened this issue Aug 4, 2020 · 0 comments
Open

Implement request status polling #740

howjmay opened this issue Aug 4, 2020 · 0 comments
Labels
A-api Area - Add/Revoke/Refactor APIs exposed by TA C-feature Category - feature P-high Priority - High, important issues or features

Comments

@howjmay
Copy link
Contributor

howjmay commented Aug 4, 2020

Currently, tangle-accelerator would distribute request id per request which would cause the client, an edge device, a burden to remember this information
Another proposal listed below will replace the current solution.

Client would generate a unique user-id by itself. The user-id may be generated from hardware information.
If client sent a request with user-id, then tangle-accelerator would track the status of this request with a redis list, and the status of the request will be updated in the list. If no user-id had been provided, then tangle-accelerator would return request ID as we are doing at this moment.

All the request status and response belongs a certain user-id will be responded with another API, request_status()

Another API for deleting the user-id may be needed

@howjmay howjmay added A-api Area - Add/Revoke/Refactor APIs exposed by TA C-feature Category - feature P-high Priority - High, important issues or features labels Aug 4, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-api Area - Add/Revoke/Refactor APIs exposed by TA C-feature Category - feature P-high Priority - High, important issues or features
Projects
None yet
Development

No branches or pull requests

1 participant