Thread:Talk:Requests for comment/API Future/REST API vs. the rest of API/reply

Svick, thanks for your comment. I don't want to completely split them up. Rather, have a separate action that is documented to only result in json, have fewer parameters, be REST-full in nature, and have some URL rewrites that simplify beginner usages as well as URL-based caching. This solves the use-case and caching issues, and at the same time reuses most of the internal API infrastructure. Advanced uses will still require api.php?... approach simply because its not as easily cache-able and have substantially larger set of capabilities. I understand that this is not ideal in terms of full consistency, but given the radically different use cases and goals, this seems like a good compromise.