Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of tmueller@day.com designates
 207.126.148.88 as permitted sender)
MIME-Version: 1.0
Date: Thu, 11 Feb 2010 12:54:29 +0100
Message-ID: <91f3b2651002110354oefb3096k8a7c7d496eb1a40a@mail.gmail.com>
Subject: Jackrabbit 3: extracting same name sibling support from the core
From: =?ISO-8859-1?Q?Thomas_M=FCller?= <thomas.mueller@day.com>
To: dev@jackrabbit.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi,

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).

Regards,
Thomas