Hi Vincent, > > No it wouldn't make sense. You would instead directly > modify the Orange > > resource, either directly from the browser or via some > edition pages (to > > allow multi-page edition for example). > > But then how you return to the main page after you've > modified the orange?
You add a query parameter with an URI to return to after edition: /orange/editor?return=/main?orange=picture&apple=text > Now we're saying that the orange needs not be aware > of the apple (the links are managed at a higher level > (the main page)); Yes, unless there was a natural link between oranges and apples, which is not the case here. > So what does the PUT operation return? A description of the orange? > It's not what we need. a > /main?orange=picture&apple=text uri? But how does the orange > know it has to include the apple? The orange never includes the apples, only the main page resource does include both of them. To make sure we are on the same page, do you agree that the following URIs identify different resources? - "/main" - "/main?orange=picture" - "/main?orange=picture&apple=text" - "/main?orange=picture&apple=picture" Best regards, Jerome
