jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-264) MicroKernel.diff for depth limited, unspecified changes
Date Tue, 21 Aug 2012 09:45:37 GMT

     [ https://issues.apache.org/jira/browse/OAK-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Mueller updated OAK-264:
-------------------------------

      Priority: Minor  (was: Major)
    Issue Type: Improvement  (was: Bug)
    
> MicroKernel.diff for depth limited, unspecified changes
> -------------------------------------------------------
>
>                 Key: OAK-264
>                 URL: https://issues.apache.org/jira/browse/OAK-264
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mk
>            Reporter: Thomas Mueller
>            Priority: Minor
>
> Currently the MicroKernel API specifies for the method "diff", if the depth parameter
is used, that unspecified changes below a certain path can be returned as:
>   ^ "/some/path"
> I would prefer the slightly more verbose:
>   ^ "/some/path": {}
> Reason: It is similar to how getNode() returns node names if the depth limited: "some":{"path":{}},
and it makes parsing unambiguous: there is always a ':' after the path, whether a property
was changed or a node was changed. Without the colon, the parser needs to look ahead to decide
whether a node was changed or a property was changed (the token after the path could be the
start of the next operation). And we could never ever support ':' as an operation because
that would make parsing ambiguous.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message