IBM沒有聲明與其它JSSE提供方的互*作*。
為了方便起見，而不干擾實現整個JSSE客户端和服務器端的代碼，我們決定去掉JSSE的功能(在圖6中的talker類)來提供虛構的XML消息。
將JSSE這樣架構以便其能夠提供兩套接口：一套被稱為服務提供方接口(ServiceProvider Interface,SPI)，而另一套是應用程序編程接口(ApplicationProgrammingInterface,API)。
In this case, JSSE will choose whichever certificate it sees fit.
The JSSE programming model enables the use of multiple such credential stores by way of maintaining a separate SSL context per individual target interaction.
不管您如何選擇實現本文演示的高級JSSE定製，任何一個都不是隨便就可以實現的。
While JSSE does start the handshake automatically, it only does so when data is first sent across the socket.
JSSE is architected such that it provides for two sets of interfaces: one is referred to as the Service Provider interface (SPI) and the other one is an Application Programming interface (API).
All this is done transparently for you by the JSSE runtime.
當將JSSE用於SSL通信時，需要在本地存儲中維護一套信任的簽名者的*書，由此得名信任庫。
JSSE 1.0.3 includes installation instructions for adding the package to the JRE, which I will not repeat here.
For expediency, rather than bother to implement the full JSSE client and server code, we decided to stub the JSSE functionality (the Talker class in Figure 6) to supply dummy XML messages.
通過構造一個定製的套接字工廠，我們可以定製JSSE的行為。
By constructing a customized socket factory we can customize the behavior of JSSE.
IBM makes no claim of interoperability with other JSSE providers.
國文精選館
