river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Hobbs" <tom.ho...@sucfin.com>
Subject RE: Use of socket factory in LookupLocator
Date Tue, 10 Nov 2009 13:07:45 GMT
I'm siding with Sim on this one.  It seems strange to use a
(comparatively) heavy weight Configuration object for this when just
overloading the constructor makes sense for the class concerned.  (And
has minimal impact elsewhere).

Two caveats though;

1) It's an *overloaded* cntr, please don't remove any of the existing
2) Leave applying the patch until after the AR2 release

I'd also be wary of discouraging the submission of a patch because we
can't decide exactly what it should look like.  I'm not convinced that
the arguments for the Configuration object are stronger than the
arguments to make this an additional cntr.  Given that, and the fact
that someone has a patch already waiting, let's go with whatever we have

Of course, if the cntr approach appears to be wrong at some point in the
future, *whoever creates the Configuration object patch* can deprecate

As some one way brighter than me once said, "a man who has never made a
mistake, has never made anything".  I say use this patch, at the very
least we can say that the River community has made something.


-----Original Message-----
From: Sim IJskes - QCG [mailto:sim@qcg.nl] 
Sent: 10 November 2009 10:40
To: river-dev@incubator.apache.org
Subject: Re: Use of socket factory in LookupLocator

Patrick Wright wrote:
> I think the point may be that the non-Configuration parameters to a
> class are generally those which must be supported by a qualifying
> implementation; whatever is in the Configuration is an internal
> decision of a specific implementation. I think host and port make
> sense as part of the LL API, whereas how sockets are created or
> configured is an implementation decision for a Jini implementation.
> For example, an implementation may decide to keep the socket factory
> itself private to the class, while allowing certain socket parameters
> like timeout to be configured via Configuration.

It was a sensible decision to include a socket factory parameter in 
SslEndpoint, TcpEndpoint, HttpEndpoint. They all don't use a config 

A LookupLocator does not need a config either. The constructor can be 
the same as an Endpoint (host,port,factory).

Gr. Sim

QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
Quality Consultancy Group b.v., Leiderdorp, Kvk Leiden: 28088397


Sucden Financial Limited, Plantation Place South, 60 Great Tower Street, London EC3R 5AZ
Telephone +44 203 207 5000

Registered in England no. 1095841
VAT registration no. GB 446 9061 33

Authorised and Regulated by the Financial Services Authority (FSA) and entered in the FSA
register under no. 114239

This email, including any files transmitted with it, is confidential and may be privileged.
It may be read, copied and used only by the intended recipient. If you are not the intended
recipient of this message, please notify postmaster@sucfin.com immediately and delete it from
your computer system.

We believe, but do not warrant, that this email and its attachments are virus-free, but you
should check.

Sucden Financial Limited may monitor traffic data of both business and personal emails. By
replying to this email, you consent to Sucden Financial 's monitoring the content of any emails
you send to or receive from Sucden Financial . Sucden Financial is not liable for any opinions
expressed by the sender where this is a non-business email.

The contents of this e-mail do not constitute advice and should not be regarded as a recommendation
to buy, sell or otherwise deal with any particular investment.

This message has been scanned for viruses by Mimecast.
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message