needing to use "SSL" for tlsClientParameters secureSocketProtocol attribute?

[Glen Mazza]

Hi, the CXF documentation, on the SSL configuration page[1], refers us 
to a 2007 blog entry[2] which stresses a need to add a 
"secureSocketProtocol="SSL" attribute/value pair to the 
http:tlsClientParameters element as the blogger illustrated below:

 <http:conduit 
name="{https://myhost.com/this/is/namespace}MyPortName.http-conduit";>
       <http:authorization>
           <sec:UserName>usernamehere</sec:UserName>
           <sec:Password>passwordhere</sec:Password>
       </http:authorization>
       <http:tlsClientParameters secureSocketProtocol="SSL">
       </http:tlsClientParameters>
</http:conduit>

This is instead of relying on the default "TLS" value.  Question: in 
this day and age, is there any reason to explicitly set this to "SSL" 
instead of relying on the default TLS value?  If no (or exceedingly 
rare), I might remove the reference to the blog article to reduce confusion.

Thanks,
Glen

[1] 
http://cxf.apache.org/docs/client-http-transport-including-ssl-support.html#ClientHTTPTransport%28includingSSLsupport%29-ConfiguringSSLSupport

[2] 
http://techpolesen.blogspot.com/2007/08/using-ssl-with-xfirecxf-battling.html

--
Glen Mazza
Talend Community Coders - coders.talend.com
blog: www.jroller.com/gmazza