|Version 11 (modified by 14 years ago) ( diff ),|
This page hosts detailed specifications for Blueprint for the RESTful API.
Web2Py generates URLs in this format:
These are generally fairly RESTful anyway, e.g.:
/sahana/gis/add_feature /sahana/gis/list_features /sahana/gis/display_feature/1 /sahana/gis/update_feature/1
Is there much benefit in chaning to URLs like:
/sahana/gis/feature/create /sahana/gis/feature/list /sahana/gis/feature/list_add /sahana/gis/feature/display/x /sahana/gis/feature/update/x
We want to be able extending this for exporting raw data in other formats, e.g. using the optional vars:
Web2Py already supports export as JSON, CSV & RTF.
- New SQLROW to JSON function: http://groups.google.com/group/web2py/browse_thread/thread/dfb65087574c24f1
- For XML Parser discussions, look at BluePrintGISImportExport
It would be best for us to add support to the framework to make it easy for module writers to have this functionality within their controllers.
Discussion of changes to Web2Py to make it more RESTful:
NB Web2Py currently doesn't support HTTP PUT/DELETE/UPDATE (only GET).
This means a little work in clients but isn't too bad if we maintain consistency: no variations between add/create, view/display, edit/update, etc
Allows multiple client UIs
REST instead of SOAP
Less bloat, more GIS-friendly.
- Second Generation Web Services: http://www.onlamp.com/pub/a/php/2003/10/30/amazon_rest.html
- Implementing REST Web Services: Best Practices and Guidelines: http://www.xml.com/pub/a/2004/08/11/rest.html
- Common REST Mistakes: http://www.prescod.net/rest/mistakes/
- How to Create a REST Protocol: http://www.xml.com/pub/a/2004/12/01/restful-web.html