Re: [infinispan-dev] QueryIterator inconsistencies

>>> Any comments / other ideas? >>> >>> Marko >> That's a lot of changes needed. One would say we could deprecate all >> methods and rewrite the new ones, but wouldn't it be better to >> deprecate the interface and introduce a brand new one? >> What about "ResultsIterator" ? after all, we're not iterating on queries.. > I agree. The only thing that bothers me is that CacheQuery would then > need new methods called (lazy)resultIterator() (instead of iterator(), > which already exists). Right. though I like "resultIterator()" more so we're having luck in this case ;) Any better suggestion for names? Anyone thinks it's worth to remove the old ones without a deprecation step to reuse the old names?