On Jan 11, 2010, at 10:01 AM, Simon Gaeremynck wrote: > Yes, I guess that could work. > > But then you can still do node.1000000.json which results in the same thing. > > I took the liberty to write a patch which checks the amount of resources will > be in the result. > If the result is bigger than a pre-defined OSGi property (ex: 200 resources) > it will send a 206 > partial content with the dump of 200 resources and will ignore the rest. > > It can be found at http://codereview.appspot.com/186072 > > Simon
Sorry, that would violate HTTP. Consider what impact it has on caching by intermediaries. Generally speaking, treating HTTP as if it were a database is a bad design. If the server has a limit on responses, then it should only provide identifiers that remain under that limit and forbid any identifiers that would imply a larger limit. An easy way to avoid this is to respond with 300 and an index of available resources whenever the resource being requested would be too big. The client can then retrieve the individual (smaller) resources from that index. ....Roy
