Request/reply discussion, 15:00 UTC Monday May 23rd 2022

[asyncapi-bot]

Meeting Info	Details
Purpose	Request and reply is a long outstanding feature request, this meeting is for discussing how not only to move forward, but also ways how to solve it. See more here: asyncapi/spec/issues/94
Time	15:00 UTC | Translate to your time zone with the time zone converter.
Meeting Place	Link
Zoom	Join live.
YouTube	Watch live and interact through live chat.
Twitch	Watch live.
Twitter	Watch live.
LinkedIn	Watch live.
More Info	Details
Meeting Recordings	Recording.
AsyncAPI Initiative Calendar	Public URL.
iCal File	Add to your calendar.
Newsletter	Subscribe to get weekly updates on upcoming meetings.

Agenda

Don't wait for the meeting to discuss topics that already have issues. Feel free to comment on them earlier.

1. Q&A
2. Place for your topic
3. Q&A

Notes

Add notes here after the meeting.

[jonaslagoni]

Following last meeting @GreenRover when you know where to pickup from last meeting feel free to ping me 🙂

[GreenRover]

@jonaslagoni @fmvilas Here are the results of the todays discussion: asyncapi/spec#94 (comment)
Hopefully i was able to remember everything, if not please pm me.

I will lets this review some architects that i proxied. And maybe update the comment later.

Still open points:

correlationId
do we need it also as well defined field? As in async api v2: https://www.asyncapi.com/docs/specifications/v2.4.0#correlationIdObject
If yes here is the same problem, is it in body or header?
Or do we just say, it is part of the body and it should be best practice to put in the field description that the server needs to copy this to the response message.

[jonaslagoni]

Recording is out: https://www.youtube.com/watch?v=ysa3xxxlUpk