| Section |
|---|
| Column |
|---|
From the point of view of the user interface, most web applications can be thought of simply as CRUD (Create, Retrieve, Update & Delete) operations on documents. In the diagram below, the form is being used to initially display a Customer and Order and then to update them. If you think in REST terms, the form is a View Resource that composes multiple Entity Resources (in this case a Customer Resource and an Order Resource), displays their current state and allows you to update them.  Image Removed Image Added
provides a very flexible and powerful mechanism for interacting with documents (and the web in general). You can download source code and forms for the discussion below. We strongly recommend that you download the example, study it and use it as a template for integrating with your own web applications. |
|
...
That's it. As usual, you access the form using its URl. When the form is used (instantiated), you may specify one or more query parameters along with the URI. For this example, we might use a URI and query parameter: .../form/1234?customer=02. will resolve the URI template above to: .../customers/02, GET the customer, and display the initialized form. When the form is submitted, will automatically PUT the customer document to the same URI thereby updating the customer. The diagram below shows the interactions.
Image Removed
Image Added
Here's an example form that uses the Customer entity described above. In the example:
...