GitHub user chrisdutz added a comment to the discussion: Refactor the Subscription API?
So right now I think the process should look like this: - A user issues a SubscriptionRequest - He gets back a SubscriptionResponse - This SubscriptionResponse returns a map of return codes, that indicate for each tag of the subscription, if subscribing that tag worked - It also contains one SubscriptionHandle - The user registers listeners to that handle - All registered callbacks start receiving data - As soon as the user no longer wants the subscription, he calls "unsubscribe()" or "close()" or whatever on the SubscriptionHandle The API function "unsubscribe" would be removed from the connection API. GitHub link: https://github.com/apache/plc4x/discussions/1037#discussioncomment-6563151 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
