Julian Reschke wrote:
Returning ItemInfos in a batch is not going to happen for the children
of a large collection. After all, the SPI impl has no idea whether the
caller wants to see them.
You have a point there.
I think with NodeInfo.getChildInfos() we should be able to efficiently traverse
nodes with reasonable sized child node entries, assuming an implementation
returns child infos and adds the child node infos to a batch read. But I agree
with you that the use case with a large collection is not solved.
hmmm, what's the exact reason we have ChildInfo? what's the downside of getting
rid of ChildInfo and use NodeInfo instead?
i.e. RepositoryService.getChildInfos() returns NodeInfos instead of ChildInfos.
regards
marcel
