> I concur with you about the difficulty of matching all the IP addresses. > That should be much easier once we migrate to Java 1.4 (using the > NetworkAddress class), but for now it's definitely a problem for complex > IP setups. However for simple IP setups I think this change would make > life substantially easier.
I can see that, but following the principle of least surprises leads me to propose documenting this as a "feature" , rather than doing half a job. > I'm not sure why we'd have to support both forms. From my reading of > the RFC, only the bracketed form is strictly correct for IP addresses. Correct. > How about we make it an optional behavior with a config param? Ok, a fine compromise, if we add (and document) a section <serveraddresses> equivalent to <servernames> with an autodetect element/parameter, as for servernames that should allow simple situations to be detected, complex situations to override it, and the chosen behaviour to be clearly seen in the configuration. I think it should be composed of <address>xxx.xxx.xxx.xxx</address> elements which are added in [] to the servernames collection. Yes? d. > > --Peter > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
