Changes between Version 25 and Version 26 of BluePrintREST

Timestamp:

01/01/09 12:13:34 (16 years ago)

Author:

Fran Boon

Comment:

Done Deal :)

BluePrintREST

@@ -10 +10 @@
 /application/controller/function/arg1/arg2?var1=x,var2=y
 }}}
-These are generally fairly RESTful anyway, e.g.:
+These are generally used in a slightly RESTful way anyway (resources are URLs), e.g.:
 {{{
 /sahana/gis/add_feature
@@ -18 +18 @@
 /sahana/gis/update_feature/1
 }}}
-We can easily change to URLs like these (see [wiki:BluePrintRESTImplementation BluePrintRESTImplementation]):
+We have changed to URLs like these (see [wiki:BluePrintRESTImplementation BluePrintRESTImplementation]):
 {{{
 /sahana/gis/feature           # Acts as 'list' (or list_add if t2.logged_in)
@@ -27 +27 @@
 /sahana/gis/feature/delete/id
 }}}
-or potentially these:
+we could potentially do these:
 {{{
 /sahana/gis/feature/id?method=display
@@ -33 +33 @@
 /sahana/gis/feature/id?method=delete
 }}}
-NB T3 requires ID to be the last argument, so don't want URLs like: /id/create
+but T3 requires ID to be the last argument, so don't want URLs like: /id/create
 
-There are benefits:
+These are the benefits:
  * Consistency & ease of implementation of all basic functionality for new tables.
  * Simplified ability to create .represent widgets:
@@ -46 +46 @@
     return DIV(*items)
 }}}
-
-There are downsides:
- * Controller functions are more complex:
-  * Need lots of extra indentation
-   * if method=='':
-   * if t2.logged_in:
 
 We want to extend this to export raw data in other formats, e.g. using the optional vars: