https://bugzilla.wikimedia.org/show_bug.cgi?id=38891
--- Comment #6 from Daniel Friesen <[email protected]> 2012-08-24 16:07:20 UTC --- Fancy urls require extra configuration and are not always available. So while they have an advantage for user-facing urls I don't think we'll ever have a valid rationale for fancy api urls. It will only make using the api harder since clients will now have to figure out what format an individual wiki is using before they can even use the api. And they'll need to write the same thing twice to do it both ways. Also you're focusing around the simple actions and forgetting how powerful the api format we have can be. Allpages fed into prop=revisions as a generator to get latest revision data from all pages: https://localhost/w/api.php?format=json&action=query&generator=allpages&prop=revisions General siteinfo about the wiki, the namespace map, the logged in user information, and some of the latest changes to the wiki. All packed into one request. https://localhost/w/api.php?action=query&format=jsonfm&meta=siteinfo|userinfo&siprop=general|namespaces&list=recentchanges This part is something I'd actually like to see more. One advantage to wrapping everything in actionname is that it's completely possible to expand our current api to support multi-action api commands. eg: Use action=query&prop=revisions and action=tokens at the same time to grab the revision text of a page and an edit token so that with your next request you can make an edit. I had an idea lying around somewhere on how to make the api capable of doing more at once. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- 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
