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

Break the relationship between writers and session/subscription #2295

Closed
marcschier opened this issue Jul 22, 2024 · 0 comments
Closed

Break the relationship between writers and session/subscription #2295

marcschier opened this issue Jul 22, 2024 · 0 comments
Labels
feature request New feature or request
Milestone

Comments

@marcschier
Copy link
Collaborator

To better support UNS and aggregation servers that are optimized for low number of subscriptions with large number of monitored items and to support large number of writers (tag writers) we must separate the subscription management from the writer concept, and split monitored item notifications to individual writers. The current model of using a topic context breaks because metadata collection is at the subscription level, it should be at the writer level. The simple way would be to make the subscription "writer aware". Pulling the writer concept out and handling somewhere else would be also possible, current POC though shows the work is large and impactful.

@marcschier marcschier added the feature request New feature or request label Jul 22, 2024
@marcschier marcschier modified the milestones: Future, 2.9.11 Jul 22, 2024
@marcschier marcschier modified the milestones: 2.9.11, 2.9.12, Future Aug 7, 2024
marcschier added a commit that referenced this issue Sep 3, 2024
* Break relationship between writers and subscription (part 1) #2295
* Updated docs and dependencies
* #2329
* #2328
* #2327
@marcschier marcschier modified the milestones: Future, 2.9.12 Sep 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant