[jira] Commented: (JCR-1166) JCR2SPI does not provide actual size on RangeIterator.getSize()

2007-11-27 Thread angela (JIRA)
[ https://issues.apache.org/jira/browse/JCR-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545873 ] angela commented on JCR-1166: - for the record (translation of oral communication): the problem julian is referring to is 2

[jira] Commented: (JCR-1166) JCR2SPI does not provide actual size on RangeIterator.getSize()

2007-11-23 Thread angela (JIRA)
[ https://issues.apache.org/jira/browse/JCR-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545021 ] angela commented on JCR-1166: - noe... you get the size immediately. but it may not be totally accurate if nodes are remove

[jira] Commented: (JCR-1166) JCR2SPI does not provide actual size on RangeIterator.getSize()

2007-11-23 Thread Julian Reschke (JIRA)
[ https://issues.apache.org/jira/browse/JCR-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545012 ] Julian Reschke commented on JCR-1166: - But that would still require to completely iterate through what the SPI imp

[jira] Commented: (JCR-1166) JCR2SPI does not provide actual size on RangeIterator.getSize()

2007-11-22 Thread angela (JIRA)
[ https://issues.apache.org/jira/browse/JCR-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544864 ] angela commented on JCR-1166: - i would suggest modify the LazyItemIterator to apply the same logic as present currently in