[OASIS Issue Tracker] (OSLCCORE-186) Server response options to pageSize=value are too vague

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Martin Sarabura created OSLCCORE-186:
----------------------------------------

             Summary: Server response options to pageSize=value are too vague
                 Key: OSLCCORE-186
                 URL: https://issues.oasis-open.org/browse/OSLCCORE-186
             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
          Issue Type: Bug
          Components: Core
            Reporter: Martin Sarabura
            Assignee: James Amsden


Currently the core spec says "OSLC ServicesÂ_may_Âignore oslc.pageSize."

What this probably means is it could respond with the requested number of values, or it could respond with no paging at all, or it could respond with a different number of values than what was requested. Which means, there really aren't any constraints on the server when the client makes this request, in which case we may as well drop this request option entirely since it duplicates the functionality of oslc.paging=true. Assuming we want to get value from oslc.pageSize, we should probably differentiate between servers that can do paging and simply choose to not do so, or servers that can't support paging at all. Not sure what to do about that but some guidance on discoverability may be in order.



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)