Ok, this is done as David has suggested. The implementation requires some little clean up but that is just a minor task and should not have further effect to API or functionality.
Stephan -----Original Message----- From: Florian Müller [mailto:[email protected]] Sent: Mittwoch, 5. Mai 2010 12:34 To: [email protected] Subject: RE: Iterable +1 I agree with David, keep getPageNumItems(). Florian -----Original Message----- From: David Caruana [mailto:[email protected]] Sent: Mittwoch, 5. Mai 2010 11:37 To: [email protected] Subject: Re: Iterable On 5 May 2010, at 09:59, Klevenz, Stephan wrote: > Hi, > > I did fix this issue and decided to re-name the Iterable to ItemIterable. I'm > not sure if we have a consensus on the naming, but the naming can change > again easily. > > https://issues.apache.org/jira/browse/CMIS-200 > > Furthermore I would like to support Florents idea to eliminate the Iterator > interface and would propose the following: If you mean collapse Iterator and Iterable then +1. > > ItemIteraror to be eliminated > long getPosition() -> eliminate method, only required for > implementation +1 > long getPageNumItems() -> eliminate -> no use case The use case is to determine how many items are in the collection backed by the iterator without iterating through them all first. For example, to display the number of items (or range of items) in the current page of query results. I don't know of any other way. > ling getTotalNumItems() -> move to ItemIterable +1 > > WDYT > > Regards, > Stephan >
