[OASIS Issue Tracker] (OSLCCORE-168) In the TRS spec, describe ways to ensure clients can read base+change log after pruning/rebase

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

Nick Crossley created OSLCCORE-168:
--------------------------------------

             Summary: In the TRS spec, describe ways to ensure clients can read base+change log after pruning/rebase
                 Key: OSLCCORE-168
                 URL: https://issues.oasis-open.org/browse/OSLCCORE-168
             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
          Issue Type: Improvement
          Components: TRS
            Reporter: Nick Crossley
            Assignee: Nick Crossley


Suppose a server has a very large number of tracked resources, and it takes a long time (weeks) to read the base, plus the change log, plus GET each of the tracked resources. Suppose a client is in the middle of that long activity when the server updates or replaces the base, and truncates the change log. The specification should have at least non-normative text describing how the server might provide sufficient information for the client to work in this case.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)