Description
Container issues for collecting tasks related to remoting the Oak API. Such a remoting should be:
- stateless on the Oak side apart from the apparent persisted state in the content repository,
- independent from oak-jcr, but reusing JCR related plugins from oak-core as required (e.g. for name space and node type handling),
- agnostic of any protocol bindings,
- ...