Skip to content

Specification for asynchronous callbacks #408

@cookeac

Description

@cookeac

Asynchronous services and tasks may result in data being updated outside of the usual timeframe of a GET message.
There may also be cases where exceptions should be raised.

@erwinspeybroeck gave some examples of how this works in the CRV system. An example is animal registration status notifications.

Possible solutions:

  • Update the original event, with its modified date/time and GET using normal methods (including synchronisation API)
  • Use Webhooks (potentially with a proxy)
  • Use Webhooks and also provide an API where an online/offline client can pick up notifications
  • Some other publish/subscribe mechanism

Two specific cases:

  • Status changes for external systems such as registration
  • Functional errors or validation errors (for instance, from external systems, a problem that needs to be resolved)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions