jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guo Du <mrdu...@gmail.com>
Subject Re: Jackrabbit 3: extracting same name sibling support from the core
Date Thu, 11 Feb 2010 12:14:03 GMT
On Thu, Feb 11, 2010 at 11:54 AM, Thomas Müller <thomas.mueller@day.com> wrote:
> About SNS (same name siblings): what about moving that part away from
> the "core"? Currently, the Jackrabbit architecture is (simplified):
> 1) API layer (JCR API, SPI API)
> 2) Jackrabbit core, which knows about SNS
> After moving the SNS support, it would be something like this:
> 1) API layer (JCR API, SPI API)
> 2) SNS support code, which knows about SNS, and maps SNS node names
> to/from internal node names
> 3) Jackrabbit core, doesn't know anything about SNS (node names must
> be unique, "[" and "]" are supported within node names)
> My hope is that this would simplify the core, because it doesn't have
> to deal with SNS at all. Disadvantage: there is a risk that certain
> things would get a bit slower if SNS are actually used (specially if
> there are lots of SNS).
Is this could be an optional feature in 3.X? As JCR 2.X is out and it
could raise comparability problem, right?

Personally I don't like/use SNS in a navigatable content system. To be
safe, I created customized node type use sameNameSiblings="false" as a
base for all my nodes:)


View raw message