On Sat, Mar 23, 2013 at 9:15 AM, Carl (CBM) <cbm.wikipedia(a)gmail.com> wrote:
On Thu, Mar 21, 2013 at 8:03 PM, Brad Jorsch
Remember that clients should not be depending on
the specific query string data returned inside the query-continue node, with either the
old-style or new style continuation.
I am not certain what this means. The names of the continuation
parameters have long been documented in the API spec at
Not exactly. It is documented that 'uccontinue' may be used for
continuation, because all possible parameters to a module are
documented. But it is not documented anywhere that 'ucstart' might be
returned inside the query-continue node instead, even though this
could currently be the case (and note this is another candidate for
bug 24782 fixing).
The established system was that the content of the
parameters is opaque, but the names of the continuation parameters are
always the same. So for "old-style" continuation we were free to
hard-code the string "eicontinue" into an API client because that was
part of the documented spec.
I see the documentation on query-continue has been moved to
as part of
the zealous pushing of the "new-style" continuation, but it does state
that both keys and values should not be counted on. Earlier versions
don't seem to have made it clear how continuation works at all.