Skip to content

[Feature Request] Support streaming responses #542

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
koepalex opened this issue Mar 4, 2025 · 2 comments
Open

[Feature Request] Support streaming responses #542

koepalex opened this issue Mar 4, 2025 · 2 comments

Comments

@koepalex
Copy link
Contributor

koepalex commented Mar 4, 2025

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
Copy link
Contributor Author

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

@avishekpant
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants