river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patrick Wright <pdoubl...@gmail.com>
Subject Re: Use of socket factory in LookupLocator
Date Tue, 10 Nov 2009 09:32:14 GMT
No, the standard approach would be that the LookupLocator constructor
would take a Configuration object, and the specification/API would
specify which keys would be read from the configuration to configure
the locator. See the APIs for net.jini.discovery.LookupDiscovery, for
example.


> Yes, but in order to configure a LookupLocator, you need a constructor to
> specifiy in the config file.
>
> like
>
> a.b.c {
>        socketFactory = new MySocketFactory();
>        lookupLocator = new LookupLocator("jini://d", socketFactory );
> }
>
> instead of (without)
> a.b.c {
>        lookupLocator = new LookupLocator("jini://d" );
> }
>
>
> Gr. Sim
>
>
> --
> QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
> Quality Consultancy Group b.v., Leiderdorp, Kvk Leiden: 28088397
>

Mime
View raw message