[jboss-jira] [JBoss JIRA] Commented: (JBREM-703) allow for total configuration of socket via socket invoker

[Ron Sigal (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBREM-703?page=comments#action_12400915 ] 
            
Ron Sigal commented on JBREM-703:
---------------------------------

Updated:

   org.jboss.remoting.transport.bisocket.BisocketClientInvoker
   org.jboss.remoting.transport.bisocket.BisocketServerInvoker
   org.jboss.remoting.transport.sslbisocket.SSLBisocketClientInvoker
   org.jboss.remoting.transport.sslbisocket.SSLBisocketServerInvoker

   org.jboss.remoting.transport.socket.SocketClientInvoker
   org.jboss.remoting.transport.socket.SocketServerInvoker
   org.jboss.remoting.transport.sslsocket.SocketClientInvoker
   org.jboss.remoting.transport.sslsocket.SocketServerInvoker
   
In the socket and bisocket transports, the following socket parameters can now be configured:

   * keepAlive
   * keepAliveSet
   * OOBInline
   * reuseAddress
   * sendBufferSize
   * soLinger
   * soLingerDuration
   * trafficClass
   
Note that setting soLinger and slLingerDuration is equivalent to calling Socket.setSoLinger(boolean on, int linger).  The parameters may be set either by

   * using them as keys in the configuration map passed to an org.jboss.remoting.Client or org.jboss.remoting.transport.Connector constructor
   
   * calling the appropriate setter function on the appropriate client or server invoker.
   
In the sslsocket and sslbisocket transports, the following additional ssl socket parameters can now be configured:

   * enabledCipherSuites
   * enabledProtocols
   * enableSessionCreation
   
They may be configured in the same way as the socket parameters.  Note that the OOBInline parameter is ignored by the sslsocket and sslbisocket transports, since it is not supported by ssl sockets.

Unit tests:

   org.jboss.test.remoting.configuration.CustomSocketConfigurationTestCase
   org.jboss.test.remoting.transport.bisocket.configuration.BisocketServerSocketConfigurationTestCase
   org.jboss.test.remoting.transport.bisocket.configuration.BisocketSocketConfigurationTestCase
   org.jboss.test.remoting.transport.bisocket.ssl.config.SSLBisocketServerSocketConfigurationTestCase
   org.jboss.test.remoting.transport.bisocket.ssl.config.SSLBisocketSocketConfigurationTestCase
   org.jboss.test.remoting.transport.socket.configuration.SocketServerSocketConfigurationTestCase
   org.jboss.test.remoting.transport.socket.configuration.SocketSocketConfigurationTestCase
   org.jboss.test.remoting.transport.socket.ssl.config.SSLSocketServerSocketConfigurationTestCase
   org.jboss.test.remoting.transport.socket.ssl.config.SSLSocketSocketConfigurationTestCase
   
Waiting for hudson results.





> allow for total configuration of socket via socket invoker
> ----------------------------------------------------------
>
>                 Key: JBREM-703
>                 URL: http://jira.jboss.com/jira/browse/JBREM-703
>             Project: JBoss Remoting
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.2.0.Alpha7
>            Reporter: Tom  Elrod
>         Assigned To: Ron Sigal
>            Priority: Minor
>             Fix For: 2.4.0.CR1 (Pinto)
>
>
> Currently remoting does not expose all the configuration properties for a socket for the socket invokers.  Should just allow configuration of everything allowed by the jdk api for a socket to be allowed via remtoing (i.e. sendBufferSize and receiveBufferSize)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira