Tags: zqlovejyc/dotnet-sdk
Tags
Allow multiple topics to call the same endpoint (dapr#763) * Allow multiple topics to call the same endpoint Using the WithTopic builder pattern allows you to specify multiple topics that route to a single endpoint. Given the topics are unique, this should be a valid case. This change allows for a single endpoint to bind to multiple topics. Note that this can only be done via the EndpointBuilder and not the TopicAttribute. dapr#715 * Let TopicAttribute to be specified multiple times The endpoint builder allowed for multiple WithTopic calls so the attribute should match that behavior.
Allow multiple topics to call the same endpoint (dapr#763) * Allow multiple topics to call the same endpoint Using the WithTopic builder pattern allows you to specify multiple topics that route to a single endpoint. Given the topics are unique, this should be a valid case. This change allows for a single endpoint to bind to multiple topics. Note that this can only be done via the EndpointBuilder and not the TopicAttribute. dapr#715 * Let TopicAttribute to be specified multiple times The endpoint builder allowed for multiple WithTopic calls so the attribute should match that behavior.
Add an option to set Timeout for ActorProxy (dapr#748) * Add an option to set Timeout for ActorProxy Actors, by there nature, may have to wait for a long period before being allowed to execute. This could lead to long request times. The default timeout for the HttpClient being used is fairly low. This commit allows for the timeout to be set when constructing the proxy. dapr#728 * Removed extra constructor and e2e tests.
Add an option to set Timeout for ActorProxy (dapr#748) * Add an option to set Timeout for ActorProxy Actors, by there nature, may have to wait for a long period before being allowed to execute. This could lead to long request times. The default timeout for the HttpClient being used is fairly low. This commit allows for the timeout to be set when constructing the proxy. dapr#728 * Removed extra constructor and e2e tests.
Only isolate state when using reentrancy (dapr#723) Non-reentrant actors can utilize their state manager's cache for repeated calls. They should still be able to do this unless using reentrancy. Co-authored-by: Ryan Nowak <nowakra@gmail.com>
Add support for Actor Reentrancy (dapr#708) * Add support for Actor Reentrancy This commit allows for the Dapr-Reentrancy-Id header to be propogated through an actor's call chain which lets the dapr runtime allow reentrant calls. dapr#661 * Add unit/e2e tests for Actor Reentrancy * Introduce state isolation for actor reentrancy * Move state context to be fully AsyncLocal
Always pass serializer options to JSON serializer Fixes: dapr#664 This fixes an issue where we're not passing the serializer options to the deserialize method for a user-specified payload. This was just an oversight and did not behave as expected when users have customized the settings. (cherry picked from commit 710868c)
Merge pull request dapr#673 from jasonviviano/jasonviviano/typo-fix Fix Typo
PreviousNext