Changes between Version 25 and Version 26 of BluePrintREST


Ignore:
Timestamp:
01/01/09 12:13:34 (13 years ago)
Author:
Fran Boon
Comment:

Done Deal :)

Legend:

Unmodified
Added
Removed
Modified
  • BluePrintREST

    v25 v26  
    1010/application/controller/function/arg1/arg2?var1=x,var2=y
    1111}}}
    12 These are generally fairly RESTful anyway, e.g.:
     12These are generally used in a slightly RESTful way anyway (resources are URLs), e.g.:
    1313{{{
    1414/sahana/gis/add_feature
     
    1818/sahana/gis/update_feature/1
    1919}}}
    20 We can easily change to URLs like these (see [wiki:BluePrintRESTImplementation BluePrintRESTImplementation]):
     20We have changed to URLs like these (see [wiki:BluePrintRESTImplementation BluePrintRESTImplementation]):
    2121{{{
    2222/sahana/gis/feature           # Acts as 'list' (or list_add if t2.logged_in)
     
    2727/sahana/gis/feature/delete/id
    2828}}}
    29 or potentially these:
     29we could potentially do these:
    3030{{{
    3131/sahana/gis/feature/id?method=display
     
    3333/sahana/gis/feature/id?method=delete
    3434}}}
    35 NB T3 requires ID to be the last argument, so don't want URLs like: /id/create
     35but T3 requires ID to be the last argument, so don't want URLs like: /id/create
    3636
    37 There are benefits:
     37These are the benefits:
    3838 * Consistency & ease of implementation of all basic functionality for new tables.
    3939 * Simplified ability to create .represent widgets:
     
    4646    return DIV(*items)
    4747}}}
    48 
    49 There are downsides:
    50  * Controller functions are more complex:
    51   * Need lots of extra indentation
    52    * if method=='':
    53    * if t2.logged_in:
    5448
    5549We want to extend this to export raw data in other formats, e.g. using the optional vars: