On Tue, Dec 18, 2012 at 11:39 AM, Yuri Astrakhan
<yuriastrakhan(a)gmail.com> wrote:
When you make a SQL query to the server, you don't get to control the
"continue" process. You can stop and make another query with different
initial parameters. Same goes for iterating through a collection - none of
the programming languages offering IEnumerable have stream control
functionality - too complicated without clear benefits.
The difference in all those examples is that you're iterating over one
list of results. You're not iterating over a list of results and at
the same time over multiple sublists of results inside each of the
results in the main list.
Documenting the "continue" properties is a
sure way to over-complicate
API usage and remove server's ability to optimize the process in the
future, without adding any significant benefit.
No one is documenting the values of the continue properties, just how
the properties are supposed to be used to manipulate the original
query.
It seems to me that you're removing the ability for the client to
optimize the queries issued (besides forgoing the use of generators
entirely and having to make 10× as many queries using titles= or
pageids=) for no proposed benefit.