tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rainer Jung <rainer.j...@kippdata.de>
Subject Re: Making AJP secret attribute consistent
Date Thu, 13 Aug 2009 20:15:46 GMT
On 13.08.2009 20:31, Mladen Turk wrote:
> On 13/08/09 19:43, Konstantin Kolinko wrote:
>>> Other option is to use required.secret instead requiredSecret
>>> Much easier because requiredSecret isn't document, so one
>>> can only find it browsing the source code.
>>>
>>> However dunno how to make it using current property set/get methods
>>>
>>
>> I have just noticed - the following patch (as currently proposed for
>> tc6.0) is an example of implementing such a dot property
>> ("socket.unlockTimeout"):
>>
>> * Improve NIO connector shutdown time by doing shutdowns in parallel
>>    and with a timeout
>>    http://svn.apache.org/viewvc?view=rev&revision=791914
>>
>> I have not dug into details yet, though.
>>
> 
> It looks like magic ;)
> I always thought that setName(...) reflects name="...",
> now it seems it's possible to have setName(...) and socket.name="..."

A similar feature is used in the cluster. The cluster configuration has
elements for the Cluster, Membership, Sender and Receiver, but not e.g.
for the Manager. If you want to set property xxx on the cluster manager,
you can configure manager.xxx inside the Cluster element.

So the part before the dot should express some kind of related class the
param should be passed to. That would be true for request.secret, but
not for required.secret.

Regards,

Rainer

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message