search

op-cellar-git / cellar-async-api

This repo contains the specifications of the microservice APIs of the new Cellar ingestion.
0 stars 0 forks source link

response body specification #2

Open simonegasperoni opened 4 years ago

simonegasperoni commented 4 years ago

Not clear how to specify properly the type of payload and it seems it's possible specifying only a content type per message

responseBody: name: responseBody payload: type: object traits:

op-cellar-git commented 4 years ago

If dynamic content types are not natively supported by asyncapi, I see two options:

  1. We use the least verbose RDF serialization for inter-process communication, e.g., turtle, n-triples
  2. We define one channel per content-type, which results in a huge number of additional channels.

The first option seems to be the best IMO.

simonegasperoni commented 4 years ago

set of content types set up inside the message schema:

regarding the char set