Re: [API] Update TSVConnSslConnectionGet name to match other TSVConnSsl* APIs

2019-09-24 Thread Derek Dagit
> > I changing TSVConnSSLConnectionGet to TSVConnSslConnectionGet. PR > > #5937 makes this change. +1 On Tue, Sep 24, 2019 at 02:43:53PM -0700, Bryan Call wrote: > > +1 - sounds good! > > -Bryan > > > > On Sep 23, 2019, at 8:25 AM, SUSAN HINRICHS wrote: > > > > TSVConnSSLConnectionGet is t

Re: [API] Update TSVConnSslConnectionGet name to match other TSVConnSsl* APIs

2019-09-24 Thread Bryan Call
+1 - sounds good! -Bryan > On Sep 23, 2019, at 8:25 AM, SUSAN HINRICHS wrote: > > TSVConnSSLConnectionGet is the only one of the TSVConnSsl* API's that uses > SSL instead of Ssl in the function name. > > The documentation refers to TSVConnSslConnectionGet instead of > TSVConnSSLConnectionGet

[API] Update TSVConnSslConnectionGet name to match other TSVConnSsl* APIs

2019-09-23 Thread SUSAN HINRICHS
TSVConnSSLConnectionGet is the only one of the TSVConnSsl* API's that uses SSL instead of Ssl in the function name. The documentation refers to TSVConnSslConnectionGet instead of TSVConnSSLConnectionGet which is how I stumbled on this while upgrading internal plugins for 9. I changing TSVConnSSLC