Skip to content
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

Introduce "no command message support" flag for protocol adapters in the Tenant API #655

Open
sysexcontrol opened this issue Jun 13, 2018 · 0 comments
Labels

Comments

@sysexcontrol
Copy link
Contributor

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).

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

No branches or pull requests

1 participant