You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Bob Scheifler (JIRA)" <ji...@apache.org> on 2007/08/06 21:11:59 UTC

[jira] Updated: (RIVER-114) Add configuration entry to LookupDiscovery for server socket factory for multicast response listener

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

Bob Scheifler updated RIVER-114:
--------------------------------

    Component/s:     (was: com_sun_jini_discovery)
                 net_jini_discovery

> Add configuration entry to LookupDiscovery for server socket factory for multicast response listener
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RIVER-114
>                 URL: https://issues.apache.org/jira/browse/RIVER-114
>             Project: River
>          Issue Type: Improvement
>          Components: net_jini_discovery
>    Affects Versions: jtsk_2.1
>            Reporter: Ron Mann
>
> Bugtrq ID [6421994|http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6421994]  It would be helpful if the LookupDiscovery utility provided a configuration entry that permitted specifying the server socket factory to use for creating the multicast discovery response listener.  Allowing this item to be configurable would make it easier to use Jini discovery across a firewall by providing control over the port used by the listener.  The need for this additional feature arose when running a Jini client on a Windows PC, which needs to run a firewall to keep it (and the network around it) safe.

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