damienburke commented on issue #22125: URL: https://github.com/apache/pulsar/issues/22125#issuecomment-2016882088
@nodece - just to confirm, with the stated goal of "disconnecting the client" - will/should that result in the pulsar client throwing an exception? (or in other words, having the app / client code - creating the pulsar consumer & producers again) with the auth challenge approach, its super clean (for tokens at least), where all that happens is the token supplier method that was provided to the client when it was instantiated is (lazily) executed. No pulsar client exception is thrown in this case, and of course the pulsar consumers and producers that were created by the pulsar client can stay connected and authenticated. Understood that for TLS this is not an option - but I just wanted to compare and understand the pulsar client behaviour that would result from the changes being discussed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
