https://bugzilla.wikimedia.org/show_bug.cgi?id=72415
--- Comment #1 from Brad Jorsch <[email protected]> --- (In reply to Michael M. from comment #0) > Just don't show a warning for meta submodules (I think these are the only > that can't be continued). meta=allmessages might return continuation (using amfrom), if the combined text of all the messages being returned exceeds $wgAPIMaxResultSize. If all the requested values for siprop don't fit, meta=siteinfo might return 'siprop' as a continuation. > 1. Don't show a warning for queries with an explicit limit=1, as these are > the queries that the user most likely doesn't want to continue. I'm not so sure about that. In bot code I've written, there are cases where I use limit=1 because I don't want to fetch a lot of unnecessary data when I expect that 99% of the time the first result will be what I need but where I do continue if necessary. And someone who has to pay per megabyte may do that more often than I do. > 2. Don't set the warning directly, but add a parameter to the continuation > data, i.e. return > > "query-continue": { > "revisions": { > "rvcontinue": 115406, > "showwarning": "" > } > } > When the client continues the query, he should add all parameters from the > continuation data, so he will include the showwarning parameter in the next > query, which can be used to show the warning in the second answer. OTOH, that doesn't show the warning on the original query. > 3. Provide a nocontinue parameter, which can be used by the client to > suppress both the warning and the continuation data. If the client wants to suppress the warning, they should use the "continue" or "rawcontinue" parameters and just ignore the continuation data. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
