Provider response-size limitations

When a client requests a resource that an OSLC Service considers to be too large to return in one response and the client has not indicated that it desires paging (via oslc.paging or oslc.pageSize), the OSLC Service MAY redirect the client to a representation that contains partial information about the resource, as follows:

• The OSLC Service receives an HTTP GET request for a resource that exceeds size limits and URL does not include oslc.paging or an oslc.pageSize key/value pair.
• The OSLC Service returns an HTTP Status 302 redirect a URL that does include the key/values for paging, as follows:
• If the client did not indicate paging, the new redirect URL MUST include the oslc.paging pair.
• If the client indicated a page size, then the redirect URL MUST include the oslc.pageSize pair with a size value that is acceptable to the service.
• The client MAY choose to follow the redirect and receive a representation that contains partial information about the resource.

On receiving a resource representation, OSLC Clients SHOULD check for the presence of an oslc:nextPage value to determine if the representation contains partial information about the resource. If the value is present, then paging is in effect and the representation contains partial information about the resource.