[Feature Request] Support streaming responses

[koepalex]

Use case:

As a connector developer
I want to send multiple responses for the same request
So that I can reduce the size of a single response and improve the latency for the first answer.

Todo:

• Extend CommandExecutor to support multiple responses e.g.

public required Func<ExtendedRequest<TReq>, CancellationToken, Task<IAsyncEnumerable<ExtendedResponse<TResp>>>> OnCommandReceived { get; set; }

• Extend CommandResponseMetadata with ResponseMessageId as well as IsLastResponse propeties
• Extend AkriSystemProperties with ResponseMessageId (proposal ReservedPrefix + "respId")
• Extend AkriSystemProperties with LastResponse (proposal ReservedPrefix + "lastResp")

[koepalex]

@avishekpant @timtay-microsoft any ETA on the streaming support for dotnet SDK?

[avishekpant]

Hi @koepalex - We're currently reviewing all feature requests and I'll provide you with an update by the EOW.

[koepalex]

@avishekpant - any update on the ETA?

[avishekpant]

Hi @koepalex - We’ll be able to begin this in the second half of June. I’ll provide an updated ETA once we start and scope the work around that time.

[timtay-microsoft]

For additional clarity here, @koepalex , each streamed response would still have the same payload shape, right? You wouldn't need anything like <TResp1, TResp2, TResp3...>

[koepalex]

@timtay-microsoft correct, it would have the same payload shape

[koepalex]

@avishekpant - Any ETA for this topic?

[avishekpant]

@koepalex - We are working on the design of Streaming support as part of the September sprint and expect to share the ETA for the .NET deliverable by the end of September.