[jira] Updated: (RIVER-71) use configurable ServerSocketFactory to create server socket for unicast discovery

["Sim IJskes (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/RIVER-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sim IJskes updated RIVER-71:
----------------------------

    Attachment: RegistrarImpl.java.patch

patch for issue.

> use configurable ServerSocketFactory to create server socket for unicast discovery
> ----------------------------------------------------------------------------------
>
>                 Key: RIVER-71
>                 URL: https://issues.apache.org/jira/browse/RIVER-71
>             Project: River
>          Issue Type: Improvement
>          Components: com_sun_jini_reggie
>    Affects Versions: jtsk_2.1
>            Reporter: Jim Hurley
>            Priority: Minor
>         Attachments: RegistrarImpl.java.patch
>
>
> Bugtraq ID [6449005|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6449005]
> An RFE for Reggie: make it so that the ServerSocket used to      
> handle unicast discovery is created from a configurable ServerSocketFactory.    
> We've run across this when trying to run Reggie behind a firewall where a range 
> of ports is exposed--if there were a configurable ServerSocketFactory, then we  
> could specify one that allocated a ServerSocket within that range.              
>                                                                                 
> (I realize we could configure a fixed port number or open up the default        
> unicast discovery port in the firewall, but we'd like to avoid hardcoding       
> portnumbers into our configurations as much as possible, and also don't want to 
> preclude running more than one instance of Reggie on a given host.)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.