Changes between Version 14 and Version 15 of RESTController
- Timestamp:
- 11/20/09 01:13:16 (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RESTController
v14 v15 48 48 The argument list is interpreted as follows: 49 49 50 * '''empty argument list''' access to all/any records of the resource51 * '''<id>''' access to record #<id> of the resource52 * '''<method>''' <method>access to all/any records of the resource53 * '''<method>/<id>''' <method>access to the record #<id> of the resource50 * '''empty argument list''' = access to all/any records of the resource 51 * '''<id>''' = access to record #<id> of the resource 52 * '''<method>''' = ''method'' access to all/any records of the resource 53 * '''<method>/<id>''' = ''method'' access to the record #<id> of the resource 54 54 55 * '''<id>/<component>''' access to all/any component records of the record #<id> of the resource56 * '''<id>/<component>/<method>''' <method>access to all/any component records for the record #<id> of the resource55 * '''<id>/<component>''' = access to all/any component records of the record #<id> of the resource 56 * '''<id>/<component>/<method>''' = ''method'' access to all/any component records for the record #<id> of the resource 57 57 58 58 If '''<id>''' is omitted from the URL while a <method> or a <component> is specified, 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 record ID memory is automatically cleared, of course.