You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A new flag to handle a "no command-message" must be introduced in the Tenant API as part of the Adapter Configuration Format. See #654 for details.
The flag will be used by specific protocol adapters to derive that a request will not have to wait for potential commands anymore and can instead be responded directly after receiving such a message.
The default shall be false.
The handling of this flag inside a protocol adapter is not part of this issue, only the definition (and possibly the implementation of helper methods to evaluate this flag).
The text was updated successfully, but these errors were encountered:
A new flag to handle a "no command-message" must be introduced in the Tenant API as part of the Adapter Configuration Format. See #654 for details.
The flag will be used by specific protocol adapters to derive that a request will not have to wait for potential commands anymore and can instead be responded directly after receiving such a message.
The default shall be false.
The handling of this flag inside a protocol adapter is not part of this issue, only the definition (and possibly the implementation of helper methods to evaluate this flag).
The text was updated successfully, but these errors were encountered: