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

Add support for multiple bindings per server feature #25

Open
DerAndereAndi opened this issue Jun 5, 2024 · 0 comments
Open

Add support for multiple bindings per server feature #25

DerAndereAndi opened this issue Jun 5, 2024 · 0 comments
Labels
backlog To be considered in the future enhancement New feature or request

Comments

@DerAndereAndi
Copy link
Member

DerAndereAndi commented Jun 5, 2024

Multiple bindings are allowed per spec (in fact they are not prohibited).

The flow then should be:

  • The first client that writes on a specialization (combination of descriptions resulting in an ID) will have the sole write access to that ID, others will be denied, until the binding is removed
  • This requires to store a current active write access list per ...ListDataType key combinations

The current behaviour is that only one binding is allowed.

@DerAndereAndi DerAndereAndi added the enhancement New feature or request label Jun 5, 2024
@DerAndereAndi DerAndereAndi added the backlog To be considered in the future label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog To be considered in the future enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant