You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2019/06/03 19:37:14 UTC

[GitHub] [pulsar] shiv4289 opened a new pull request #4451: [Issue 4441][client]Deduce ClientConfigurationData.isUseTls from protocol

shiv4289 opened a new pull request #4451: [Issue 4441][client]Deduce ClientConfigurationData.isUseTls from protocol
URL: https://github.com/apache/pulsar/pull/4451
 
 
   ### Motivation
   There are two ways of instantiating a java client and both should behave in similar ways. As of now, PulsarClient.builder assumes tls enabled if the pulsar+ssl or https is used in the service url. In fact, the builder marks enableTls() as deprecated.
   
   ClientConfigurationData.java lags a bit that way. It does not enable tls if pulsar+ssl or https is used in service url.
   
   ### Modifications
   Deduce tls from protocol

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services