2 Replies Latest reply on Jun 17, 2008 11:01 AM by Andy Taylor

    thoughts on remoting configuration

    Andy Taylor Master

      Once we have Netty implementation for remoting and also when we have implementations for say HTTP and Servlet is the cuurent way we configure remoting going to get messy. For instance you may want an acceptor listening on TCP and HTTP and also INVM. I was thinking something similar to the following.

       <remoting acceptorType="Mina">
       <remoting-transport>TCP</remoting-transport>
       <remoting-bind-address>5400</remoting-bind-address>
       <remoting-host>localhost</remoting-host>
       <remoting-port>5400</remoting-port>
       <remoting-call-timeout>5000</remoting-call-timeout>
       <remoting-tcp-nodelay>true</remoting-tcp-nodelay>
       <remoting-tcp-receive-buffer-size>32768</remoting-tcp-receive-buffer-size>
       <remoting-tcp-send-buffer-size>32768</remoting-tcp-send-buffer-size>
       <remoting-ping-interval>10000</remoting-ping-interval>
       <remoting-ping-timeout>5000</remoting-ping-timeout>
       <remoting-enable-ssl>false</remoting-enable-ssl>
       <remoting-ssl-keystore-path>messaging.keystore</remoting-ssl-keystore-path>
       <remoting-ssl-keystore-password>secureexample</remoting-ssl-keystore-password>
       <remoting-ssl-truststore-path>messaging.truststore</remoting-ssl-truststore-path>
       <remoting-ssl-truststore-password>secureexample</remoting-ssl-truststore-password>
       </remoting>
       <remoting acceptorType="Mina">
       <remoting-transport>HTTP</remoting-transport>
       <remoting-bind-address>5401</remoting-bind-address>
       <remoting-host>localhost</remoting-host>
       <remoting-port>5400</remoting-port>
       <remoting-call-timeout>5001</remoting-call-timeout>
       </remoting>
       <remoting acceptorType="INVM">
       <remoting-host>localhost</remoting-host>
       </remoting>
      


      I think this would make it simpler for the end user, wdyt?