Changes between Version 12 and Version 13 of RESTController


Ignore:
Timestamp:
11/20/09 01:08:31 (12 years ago)
Author:
Dominic König
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • RESTController

    v12 v13  
    5656  * '''<id>/<component>/<method>''' <method> access to all/any component records for the record #<id> of the resource
    5757
    58 You may even pass a record ID for the component at the end of the arguments list to access a particular component record - which would produce an error message if these two records do not belong together.
     58If '''<id>''' is omitted from the URL while the argument list is not empty, then the last used <id> for this resource will be used. This feature can be used for cascading or returning UI actions. The last record ID can be explicitly cleared by sending a request to the primary resource with ''clear'' as method. At login/logout as well as after a ''delete'' action, the ID memory is automatically cleared, of course.
     59
     60You may pass a record ID for the component at the end of the arguments list to access a particular component record - which would produce an error message if these two records do not belong together. Component record ID's are not remembered.
    5961
    6062The data format of the request can be passed:
     
    6567
    6668If multiple extensions are specified, the rightmost extension applies. Where ''?format='' is specified, it overrides any extensions.
    67 
    68 If no ID for the primary resource record is sent in the URL, the last record ID will be remembered. This can be used for cascading or returning UI actions. This ID trace can be explicitly cleared by sending a request to the primary resource with ''clear'' as method. At login/logout as well as after a ''delete'' action, the ID memory is automatically cleared.
    6969
    7070== Model ==