Hi, Same response from me, I don't really understand this need for a new api. The current one is working correctly (at least for me), has enough documentation to let developers find their way for using it, ...
I'm currently using a lot of functions from the current API for WPCleaner [1]. I've already done the upgrade from query.php to api.php in its time, and I know that going from one api to an other again would require a lot of my time to implement and test. And without any obvious improvement. Nico [1] http://en.wikipedia.org/wiki/Wikipedia:WPCleaner On Fri, Nov 9, 2012 at 6:11 AM, Chris Grant <[email protected]>wrote: > Huge +1 for long term backwards compatibility. > > I can't quite see what problems this is trying to solve? > > Reading through > https://www.mediawiki.org/wiki/API/API_rewrite/Kickoff_meeting > I don't see any argument for why we are moving to replace the current API. > It reads more like "oh, this'll be cool"! > > That said, I'm all for making Mediawiki more accessible to > "apps"/mobile/whatever. In particular I'm thinking of o-auth (or similar), > which is long overdue. Something like that would be very helpful for > toolserver tools. > > I'm just a bit confused about why we need a new api. What are we trying to > fix? What are the goals? And most importantly, we need a clear idea of > where the current API fails. > > -- Chris > > _______________________________________________ > Mediawiki-api mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/mediawiki-api > >
_______________________________________________ Mediawiki-api mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mediawiki-api
