You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Lukas Kahwe Smith (JIRA)" <ji...@apache.org> on 2015/03/03 13:30:04 UTC

[jira] [Commented] (OAK-2414) Oak API remoting

    [ https://issues.apache.org/jira/browse/OAK-2414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14345008#comment-14345008 ] 

Lukas Kahwe Smith commented on OAK-2414:
----------------------------------------

[~frm] would be good to create a few tickets with dedicated tasks so that people can help out. it seems your private fork is the place to send patches?

> Oak API remoting
> ----------------
>
>                 Key: OAK-2414
>                 URL: https://issues.apache.org/jira/browse/OAK-2414
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: core
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: api, remoting
>
> 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,
> * ...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)