Skip to content

Accommodate asynchronous pattern #20

@bigludo7

Description

@bigludo7

Problem description
This topic is mentioned here #10 but probably deserves it owns issue.
Seems that for UCs we can provide asynchronous answer that will allow us more flexibility to handle the request.
If we want to offer this capability we need slight changes.

Possible evolution

  • add 202 as possible answer
  • add callbackurl & token in the request. By valued them the consumer expect to get an asynchronous answer and this answer will be posted to this callbackUrl

Alternative solution

  • add 202 as possible answer
  • add a requestId in the POST response & provide GET operation but this change a bit more the API

Additional context

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions