well, it's RPC oriented. 'action' is used to denote what is being done. and server side changes will be done by 'GET'. this means there's no clear partitioning of data, and no clear separation between actions that change the server side state and those that just retrieve it (which can then be cached). also, in REST, the returned information can contain urls to other pieces of information that can be naturally navigated to retrieve that information.
Brion Vibber wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Ittay Dror wrote:
have you considered REST api? it would be cleaner i think and REST apis take caching of pages into consideration (important for performance)
Can you explain for the gallery what's non-RESTy about the current draft api?
- -- brion vibber (brion @ pobox.com / brion @ wikimedia.org)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFFt7KjwRnhpk1wk44RAs8uAJwPK/WbeX6ROJ09uEdyTpxnr4Qz+QCfbLoj o+pHP/KoFolvn/Y9qNTm578= =CfhG -----END PGP SIGNATURE-----
MediaWiki-l mailing list MediaWiki-l@lists.wikimedia.org http://lists.wikimedia.org/mailman/listinfo/mediawiki-l