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

Evaluate the possible removal of SubscriptionDescription #357

Closed
sbegaudeau opened this issue Mar 1, 2021 · 0 comments · Fixed by #374
Closed

Evaluate the possible removal of SubscriptionDescription #357

sbegaudeau opened this issue Mar 1, 2021 · 0 comments · Fixed by #374

Comments

@sbegaudeau
Copy link
Member

In order to support more easily additional types of subscriptions not related to the editing context, it would be nice to not have to rely on subscription descriptions anymore

@sbegaudeau sbegaudeau self-assigned this Mar 1, 2021
@sbegaudeau sbegaudeau added this to the 0.3.0 milestone Mar 2, 2021
sbegaudeau added a commit that referenced this issue Mar 4, 2021
This first commit will make sure that the disposal of the representation event
processors do not rely on SubscriptionDescription anymore. Thanks to this commit
it will be possible to remove the SubscriptionDescription during the retrieval of
the payload flux and then to update the lifecycle of the APIs used to disposed
the representations event processors.

Bug: #357
Signed-off-by: Stéphane Bégaudeau <[email protected]>
sbegaudeau added a commit that referenced this issue Mar 4, 2021
This first commit will make sure that the disposal of the representation event
processors do not rely on SubscriptionDescription anymore. Thanks to this commit
it will be possible to remove the SubscriptionDescription during the retrieval of
the payload flux and then to update the lifecycle of the APIs used to disposed
the representations event processors.

Bug: #357
Signed-off-by: Stéphane Bégaudeau <[email protected]>
sbegaudeau added a commit that referenced this issue Mar 4, 2021
sbegaudeau added a commit that referenced this issue Mar 5, 2021
…tion event processors

Bug: #357
Signed-off-by: Stéphane Bégaudeau <[email protected]>
sbegaudeau added a commit that referenced this issue Mar 10, 2021
This first commit will make sure that the disposal of the representation event
processors do not rely on SubscriptionDescription anymore. Thanks to this commit
it will be possible to remove the SubscriptionDescription during the retrieval of
the payload flux and then to update the lifecycle of the APIs used to disposed
the representations event processors.

Bug: #357
Signed-off-by: Stéphane Bégaudeau <[email protected]>
sbegaudeau added a commit that referenced this issue Mar 10, 2021
sbegaudeau added a commit that referenced this issue Mar 10, 2021
…tion event processors

Bug: #357
Signed-off-by: Stéphane Bégaudeau <[email protected]>
sbegaudeau added a commit that referenced this issue Mar 10, 2021
This first commit will make sure that the disposal of the representation event
processors do not rely on SubscriptionDescription anymore. Thanks to this commit
it will be possible to remove the SubscriptionDescription during the retrieval of
the payload flux and then to update the lifecycle of the APIs used to disposed
the representations event processors.

Bug: #357
Signed-off-by: Stéphane Bégaudeau <[email protected]>
sbegaudeau added a commit that referenced this issue Mar 10, 2021
sbegaudeau added a commit that referenced this issue Mar 10, 2021
…tion event processors

Bug: #357
Signed-off-by: Stéphane Bégaudeau <[email protected]>
@sbegaudeau sbegaudeau linked a pull request Mar 15, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant