-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Closed
Labels
ClientThis issue points to a problem in the data-plane of the library.This issue points to a problem in the data-plane of the library.Service Busfeature-requestThis issue requires a new behavior in the product in order be resolved.This issue requires a new behavior in the product in order be resolved.
Milestone
Description
Is your feature request related to a problem? Please describe.
Users consuming autolockrenew would like a more responsive mechanism to react to issues in lock renewal. (see #11611) This would cleanly mirror the pattern used in the processors of other language sdks (onError handlers)
Describe the solution you'd like
An onError callback parameter to autolockrenewal registration or creation to allow taking immediate action if renewal fails.
Describe alternatives you've considered
There are two approaches I see to this.
- put on the initial constructor, for all registered objects.
- Put on the "register" stanza. This seems like the right choice, as action for renewal failure on a session vs. a message are very different things and one may use lock renewal for both. (Technically we could accomplish this in the generic constructor by passing the entity in question as well; but it would then require instanceof, and that's a code smell to me)
Additional context
See GH thread linked above for further context.
Metadata
Metadata
Assignees
Labels
ClientThis issue points to a problem in the data-plane of the library.This issue points to a problem in the data-plane of the library.Service Busfeature-requestThis issue requires a new behavior in the product in order be resolved.This issue requires a new behavior in the product in order be resolved.