| 0371d85fa3ecb5f162d107cdbff0a99cd987fdcc |
|
27-Jul-2010 |
Elliott Hughes <enh@google.com> |
Fix setSoLinger.
The bizarre use of Boolean or Integer (rather than just using -1) comes
from the RI. Third-party SocketImpl implementations may expect the RI's
documented behavior, so we should probably do the same.
I've also changed SocketChannelImpl.SocketAdapter to reuse Socket's
implementation of all the socket option getting/setting code, mainly so
we don't have two copies of all the weirdness.
I've also fixed a bug in the native getSocketOption code which returned
a Boolean rather than an Integer for IP_TOS/IPV6_TCLASS, though that code
is actually never called at the moment.
I've removed support for passing Byte values to setSocketOption. The RI
only uses Boolean and Integer.
Change-Id: I80ba63745f4c4f3ac357dc3f0b7cbf254a291bce
|