> I agree and would add that those lower-level resources (or core resources) > could be modelled and exposed as either: > - persistent POJOs (db4o, EJB3, etc.) > - RESTful resources (via a separate Restlet application for example) > > In the second case, you could even think about a two-layer approach, where > on Web Component would remotely access to an internal Core/Business > Component. This way, your Core Component could be shared between several > 'view' applications/components.
So, say we have a page that displays a picture of an apple and a picture of an orange. When we click on either picture, we want to replace it by the text representation of the selected fruit (we we want to keep displaying the picture of the other fruit). We have 3 resources: MainPage, Apple, Orange. Apple and Orange are what you call 'low-level' resources'; the Mainpage resource is the highest abstraction. To display the main page you GET /mainPage What are the apppe's and orange's URI's like? For the apple: /mainPage?orange=picture&apple=text For the orange: /mainPage?orange=text&apple=picture Is that what you had in mind? What if we want to modify the orange? Do we PUT the mainPage, passing it the Orange info? -vincent.
