On Jun 15, 2007, at 3:05 AM, Dennis Sosnoski wrote: > Anne Thomas Manes wrote: > > ... > > > > Note that to truly exploit the power of REST (and in particular, the > > "hypermedia as the engine of state" constraint), the response to the > > query by age should return a list of URIs for the people matching > the > > query (each person is a resource with its own URI). > > > > Does everyone agree on this last point? It seems like that's going to > make for a lot of separate requests in order to get actual information > (since the GET http://example.org/people?age=29 result is a list of > URIs). > > From the performance standpoint, it's generally going to be much more > efficient to allow the result to provide the full data for the people > matched (which would include the URI for each person as a standalone > entity). What do the REST advocates think is appropriate for a case > like > this - allow a response which includes a set of resources, or require > each resource to be accessed directly and damn the cost? >
I would suggest that for it to be "RESTful", the result should include the URIs for getting the details, but can include as much additional information inline as you like. Third normal form is certainly not a REST requirement ;-) Stefan -- Stefan Tilkov, http://www.innoq.com/blog/st/
