[jira] Commented: (JCR-1418) Redesign NodeInfo.getReferences()

["angela (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCR-1418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590353#action_12590353 ] 

angela commented on JCR-1418:
-----------------------------

i would be in favor of that improvement.

> Redesign NodeInfo.getReferences()
> ---------------------------------
>
>                 Key: JCR-1418
>                 URL: https://issues.apache.org/jira/browse/JCR-1418
>             Project: Jackrabbit
>          Issue Type: Improvement
>          Components: jackrabbit-spi
>    Affects Versions: 1.4
>            Reporter: Marcel Reutegger
>            Priority: Minor
>
> The method returns an array of PropertyIds. When there are lots of references this may become an problem. As with any other return value that potentially is large we should return an iterator.
> I suggest to redesign the handling of references in line with recent discussions how child infos are handled.
> - A NodeInfo implementation must either return the complete list of PropertyIds or null if it does not want to return the PropertyIds at that time.
> - Introduce a new method: Iterator<PropertyId> RepositoryService.getReferences(SessionInfo, NodeId)
> This has the following advantages:
> - loading of references can be delayed until it is really needed
> - large collections of references can be streamed through the SPI

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.