fix(eventstream-handler-node): start streaming without waiting for response

[kuhe]

Issue

internal V1360694816

Description

This sets the event stream payload handler to begin streaming the input payload without waiting for any server response. QBusiness does not send any initial response ack, whereas TranscribeStreaming does. However, since we don't need to handle this ack in any way, we can start the stream regardless in both cases.

Testing

import { ChatCommand, QBusinessClient } from "@aws-sdk/client-qbusiness";

const client = new QBusinessClient;

const command = new ChatCommand({
  applicationId: "49.....-....-....-....-.....c9",
  inputStream: (async function* () {
    yield { textEvent: { userMessage: "say hi" } };
    yield { endOfInputEvent: {} };
  })(),
});

const response = await client.send(command);
for await (const event of response.outputStream!) {
  process.stdout.write(event?.textEvent?.systemMessage ?? "");
}

Generating an answer based on what I know...

 Hi!

I tested TranscribeStreaming as well, and it still works.

Additional context

I'm not able to add an E2E test at this time because of the complexity of setting up the resource.

HTTP2 does not require any sort of ack to begin bi-directional streaming. That was an assumption of our legacy code given how AWS services at the time behaved.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.