From b409528cb2f76d7883e932a8d99673a89713f4b7 Mon Sep 17 00:00:00 2001 From: Rohit Date: Thu, 7 Dec 2023 20:14:24 +0530 Subject: [PATCH] Request/reply content --- 100-level-AsyncAPI-Intro/step2.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/100-level-AsyncAPI-Intro/step2.md b/100-level-AsyncAPI-Intro/step2.md index 48db9b3..4da35b6 100644 --- a/100-level-AsyncAPI-Intro/step2.md +++ b/100-level-AsyncAPI-Intro/step2.md @@ -11,7 +11,14 @@ As it is much easier to understand things in action, Eve explains each component --> Mahfuza's content regarding various components of AsyncAPI document<-- ## Request/reply +As Eve and Chan almost finish setting up the communication system, Eve explains to Chan about Request/reply pattern, which is not a component but a common communication pattern. + +Eve explains Chan that this is a type of communication pattern where there are two components, a requestor and a replier. + +Here, Eve's channel is a requestor which sends a request asking Chan how is he or vice versa. And the reply address as to where the response to her request needs to be delivered is known while defining the communication system. -- -Back to storyline and transition to module 4 with chan leaving eve's planet. \ No newline at end of file +With the final pieces programmed and the communication system in place, Chan gets ready to get back home. + +Making a promise to stay in touch, Chan takes off in his spaceship back to [Placeholder for Chan's planet] \ No newline at end of file