Status of oak-mk-remote and oak-mk

[Angela Schreiber <an...@adobe.com>]

hi michael

i just had a discussion with philipp suter and francesco mari
regarding the missing uuid uniqueness constraint validation in our
granite.js + microkernel setup, which has been reported as
vulnerability last year.

during that discussion i learned that granite.js is no longer
making use of the "oak-mk" and "oak-mk-remote" modules and
that a shared repository setup (i.e shared persistence layer
between granite.js and jcr-oak) is no longer considered a valid
use case.

since philipp didn't know about the mentioned oak modules
i would like to ask you to confirm the 2 statements above.

in case of confirmation i would go ahead and start a vote
on oak-dev for moving "oak-mk" and "oak-mk-remote" into
an attic folder and marking them as abandoned code that
should no longer be used.

thanks in advance and kind regards
angela

Re: Status of oak-mk-remote and oak-mk

[Angela Schreiber <an...@adobe.com>]

hi

today i had a private conversation with philipp and michael
and it was confirmed that the js client will no longer make
use of those as the remoting is being implemented on top
of the oak api.

will therefore follow up as proposed on oak-dev for the next steps.

kind regards
angela