<
From version < 8.3 >
edited by Silvia Macovei
on 2009/09/25
To version < 8.4 >
edited by Silvia Macovei
on 2009/09/25
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -136,7 +136,7 @@
136 136  1.1.1 Sending representations
137 137  
138 138  Many resources are modifiable, so you can send representations in order to change the state of those resources (e.g., pages).
139 -All modifiable resources accepts XML representations that conform to the [XML Schema Definition > http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-rest/src/main/resources/xwiki.rest.model.xsd]. However, some other representations might be accepted as well (see the following sections).
139 +All modifiable resources accept XML representations that conform to the [XML Schema Definition > http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-rest/src/main/resources/xwiki.rest.model.xsd]. However, some other representations might be accepted as well (see the following sections).
140 140  
141 141  Resource update is usually done by using the PUT method, while resource creation is done via PUT or POST.
142 142  
... ... @@ -181,12 +181,13 @@
181 181  
182 182  1.1.1 PUT vs POST
183 183  
184 -In the following sections you will see that sometimes resources are created by using PUT and sometimes by using POST. The general principle is that if the client is responsible of choosing the resource URI then PUT is used. If it's the server that bears this responsibility then POST is used.
184 +In the following sections you will see that sometimes resources are created by using PUT and sometimes by using POST. The general principle is that if the client is responsible for choosing the resource URI then PUT is used. If it's the server that bears this responsibility then POST is used.
185 185  
186 186  To be more clear, when a client wants to create a page it knows *where* that page should go, so it is able to communicate the server the target URI. PUT is used.
187 187  
188 -A client, on the contrary, cannot know beforehand what will be the URI of a comment, since comment URIs contains the ID of the comment and this information is generated by the server. In this case the client will do a POST and the server, in the response, will communicate the URI it generated for the newly created comment.
188 +A client, on the contrary, cannot know beforehand what will be the URI of a comment, since comment URIs contains the ID of the comment and this information is generated by the server. In this case the client will do a POST and the server, in response, will communicate the URI it generated for the newly created comment.
189 189  
190 +
190 190  1.1 XWiki RESTful API Documentation
191 191  
192 192  In this section you will find the documentation of the whole XWiki RESTful API.

Get Connected