Re: HTTP status code for "response too large"

[Jan Algermissen <[e-mail]>]

On Apr 18, 2012, at 1:41 PM, Andreas Maier wrote:

> 
> We want to support an "expand" query parameter that causes references to
> resources in the result to be expanded to the resources that they
> reference. One of the error situations in this context is that the
> expansion can lead to a result that is too large to handle for the server
> (e.g. in cases of high mutiplicities on CIM associations). The recovery for
> this situation is that the client specifies less expansions in the first
> request issues subsequent requests for separate expansion (one per
> reference, which can then be paged into multiple responses in case of high
> multiplicities).
> 
> 

[snip]

>   - Do you have a recommendation on how to handle this situation?

Sounds like a response *entity* issue more than anything else. Use paging links[1] to allow the server to split the response as it sees fit.  

Jan

[1] http://www.ietf.org/rfc/rfc5005.txt