SSL + NIO的线程安全(Thread Safety with SSL + NIO)

 有一些有用的信息可用于使用Java实现SSL与NIO (SocketChannel and SSLEngine) ，而不是使用netty等框架。 
 
 我试图提出一个SSL实现，可以使用blocking/non非阻塞通道，并获得一些基本的qns 。 
 
 当操作appData和Net缓冲区时，关于线程安全性要处理的问题没有太多信息。 根据SSLEngine的文档， 
 
 “有两个并发问题需要注意： 
 
 wrap()和unwrap()方法可以彼此同时执行。 
 
 SSL/TLS协议使用有序数据包。 应用程序必须注意确保生成的数据包按顺序传递。 如果数据包无序到达，可能会发生意外或致命的结果。“ 
 
 这适用于阻塞和非阻塞吗？ 有人可以解释一下。 谢谢。 
 
 此外，设置初始缓冲区大小的一般建议似乎是基于（ session.getApplicationBufferSize()/getPacketBufferSize() ），这些值将如何设置？ 是否更好地使用这些标准缓冲区大小为32k左右？ 

There is some helpful information available on implementing the SSL with NIO (SocketChannel and SSLEngine) using java, not using a framework such as netty etc. 
 
I am trying to come up with an SSL implementation that could work with blocking/non blocking channels and got some basic qns. 
 
There is not much info on the issues to be dealt with thread safety, when the appData and Net buffers are being manipulated. Per the documentation of SSLEngine, 
 
"There are two concurrency issues to be aware of:
 
The wrap() and unwrap() methods may execute concurrently of each other.
 
The SSL/TLS protocols employ ordered packets. Applications must take care to ensure that generated packets are delivered in sequence. If packets arrive out-of-order, unexpected or fatal results may occur."
 
Would this be applicable to both blocking and non blocking ? Could somebody explain. thanks. 
 
Also, the general recommendation for setting up the initial buffer sizes seems to based of (session.getApplicationBufferSize()/getPacketBufferSize()), how would these values be set ? Are these better to be used instead of some standard buffer size of 32k or so ?

原文：https://stackoverflow.com/questions/39792626