[jboss-jira] [JBoss JIRA] Commented: (JBREM-781) Socket transport needs to provide to the client local address of a TCP/IP connection, as seen from the server

[Ron Sigal (JIRA)]

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

A new branch remoting_2_2_0_Alpha7_JBREM-781 was created from version remoting_2_2_0_Alpha7.  The patch changes were committed and the new branch was then tagged remoting_2_2_0_Alpha7_JBREM-781-patch.

Unit test:  org.jboss.test.remoting.transport.socket.localaddress.LocalAddressTestCase.

> Socket transport needs to provide to the client local address of a TCP/IP connection, as seen from the server
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: JBREM-781
>                 URL: http://jira.jboss.com/jira/browse/JBREM-781
>             Project: JBoss Remoting
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>          Components: transport
>    Affects Versions: 2.2.0.Alpha7
>            Reporter: Ovidiu Feodorov
>         Attachments: JBREM-781.2.patch, JBREM-781.patch
>
>
> This is required by Messaging 1.0 series. See JBMESSAGING-1020 for more details.
> To get that IP address back to the client, the Remoting protocol should be modified to support a new primitive ("$GET_CLIENT_LOCAL_ADDRESS"), which is only handled by socket transports and ignored by others.
> A trip to the server is required for NAT-type of situations.

-- 
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