What?
Currently, the API is defined in a way that the requests are synchronised. E.g., a GET /shells/{id} results directly to a AAS response (if exists). In practice, however, this will most likely not be possible since creating an AAS will take some time. An async API is needed.
How?
Introduce async resources such as /shellsAsync/{id} that returns a status message (e.g., pending, running, completed or failed) with a status resource. A sample usage can be found here: https://w3c.github.io/wot-profile/#async-action-response
What?
Currently, the API is defined in a way that the requests are synchronised. E.g., a GET /shells/{id} results directly to a AAS response (if exists). In practice, however, this will most likely not be possible since creating an AAS will take some time. An async API is needed.
How?
Introduce async resources such as /shellsAsync/{id} that returns a status message (e.g., pending, running, completed or failed) with a status resource. A sample usage can be found here: https://w3c.github.io/wot-profile/#async-action-response