Open
Description
Currently, the subscription spec documents 2 responses:
- 201 Created successfully
- 400 Invalid request
The subscription create request allows a consumer to subscribe to multiple event types. As there are multiple event types requested, could there be a possibility (to avoid timeout possibilities) to respond with 202 indicating that the subscription create request has been accepted for processing but has not been finished yet?