On Jan 12, 2015, at 3:54 PM, Oliver Lietz <[email protected]<mailto:[email protected]>> wrote:
On Monday 12 January 2015 14:07:14 Antonio Sanso wrote: hi Oliver hi Antonio, On Jan 12, 2015, at 3:01 PM, Oliver Lietz <[email protected]<mailto:[email protected]>> wrote: On Friday 09 January 2015 11:28:59 Antonio Sanso wrote: Hi, We solved 4 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12329053 hi, this release introduces two new property keys which do not follow a common scheme: resource.resolver.max.vanityPath.entries and resource.resolver.vanity.bloom.filter.max.bytes As these can't be changed after release for backward compatible reasons can we align them now? sure , what is the common scheme then ? hard to find a common scheme as we already have an arbitrary use of dots, lower camel case, nouns, verbs and no hierarchy (same for other bundles): resource.resolver.default.vanity.redirect.status resource.resolver.enable.vanitypath resource.resolver.max.vanityPath.entries -> resource.resolver.vanitypath.maxEntries (or .max_entries?) resource.resolver.vanity.bloom.filter.max.bytes -> resource.resolver.vanitypath.bloomfilter.maxBytes (or .max_bytes?) resource.resolver.optimize.alias.resolution resource.resolver.vanitypath.whitelist resource.resolver.vanitypath.blacklist resource.resolver.vanity.precedence WDYT? same to me… since we do not really have a common schema and this thing is not exposed anyway… :) Regards, O. [...]
