jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tommaso Teofili <tommaso.teof...@gmail.com>
Subject Re: writing a new MK, guidelines
Date Wed, 06 Nov 2013 13:43:26 GMT
Thank you all for the very nice pointers!

Regards,
Tommaso


2013/11/6 Stefan Guggisberg <stefan.guggisberg@gmail.com>

> hi tommaso
>
> the javadoc of org.apache.jackrabbit.mk.api.MicroKernel specifies the
> API contract.
>
> org.apache.jackrabbit.mk.test.MicroKernelIT is the integration test
> which verifies
> whether an implementation obeys the contract.
>
> org.apache.jackrabbit.mk.core.MicroKernelImpl serves as a reference
> implementation
> of the MicroKernel API. it uses a GIT-inspired data/versioning model.
>
> more pointers:
> - wiki page [1]
> - versioning model as implemented by the reference implementation [2]
>
> cheers
> stefan
>
> [1] http://wiki.apache.org/jackrabbit/RepositoryMicroKernel
> [2]
> http://wiki.apache.org/jackrabbit/RepositoryMicroKernel?action=AttachFile&do=view&target=MicroKernel+Revision+Model.pdf
>
>
>
> On Wed, Nov 6, 2013 at 11:31 AM, Tommaso Teofili
> <tommaso.teofili@gmail.com> wrote:
> > Hi all,
> >
> > out of curiosity, I was wondering if there's any guideline other than
> > following the API on writing a new MK implementation.
> > What one should start with, design concepts, experience on known dos,
> > donts, caveats, etc.
> >
> > In the past I wanted to play with it a bit but never had time to do
> > anything there however that may be a useful information (if anything like
> > that exists) to share.
> >
> > Regards,
> > Tommaso
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message