Changes between Version 29 and Version 30 of RESTController

Timestamp:

04/06/10 22:49:01 (15 years ago)

Author:

Dominic König

Comment:

--

RESTController

@@ -22 +22 @@
     * [wiki:S3XRC JSON] as light-weight alternative for AJAX-style resource access
 
-== Joined Resources ==
+== Resources ==
 
-''(This extends the single-table [wiki:BluePrintRESTImplementation REST Implementation])''
+Resources are data objects of the application, which can have attributes and methods. Attribute values are stored in the data store of the application (usually the local database), while methods are provided by the controller function of the particular resource.
 
-A '''joining request''' is a request to a table ('''component''') in dependency of a join to another table ('''resource'''), e.g.:
+Attributes can be simple (=atomic types) or complex (=object types), e.g. in a "person" resource the "first_name" attribute is of an atomic type (=string), while the "address" attribute is of an object type (=pr_address). Complex attributes in S3 are also called ''Components''.
 
-  * the list of addresses (=component) of a person (=resource)
+  ''Components are stored in separate database tables which reference the primary resource record.''
 
-A resource and its components together represent a "Joined Resource".
-
-There are different ways how such joined resources can be seen:
-
-  - as database tables with embedded subtables
-  - as data objects with structured properties
-  - as compound objects with component classes
-
-In this implementation, component tables can be joined 1:1 or N:1 to their primary resources, either by natural joins (same key field in both tables) or primary/foreign key matches, where the primary key is always the 'id' field in the primary table.
-
+Resources as well as their components and methods can be addressed by URL's.
 == URL Argument Lists ==