Thanks for driving this improvement, ZengXiong.
I second ZhangJian's comments. We don't want to break the existing API (forward
compatibility) unless there are strong technical reasons that the user needs to
do minor updates in the client to migrate to a new version.
-Lari
On 2024/09/29 01:51:5
+1(no-binding) for this feature, it's common to pass tls.Config in the
Golang ecosystem(For example, current tlsOptions doesn't allow to pass
cert from memory bytes, but it's very common in golang). I tend to
proposal2, for backward compatibility, I think we can provide some
utility method to conve
Hi all
I would like to start a discussion to pass the std tlsconfig to pulsar go
client. I have two options for change.
Proposal 1: Incorporate std tlsconfig as an Externally Configurable Variable in
tlsOptions
In this proposal, I suggest adding the standard library's tlsconfig as an
op
