[OASIS Issue Tracker] (OSLCCORE-86) Provide TRS consumers with an efficient means of accessing tracked resources

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

     [ https://issues.oasis-open.org/browse/OSLCCORE-86?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Amsden updated OSLCCORE-86:
---------------------------------

    Component/s: TRS

> Provide TRS consumers with an efficient means of accessing tracked resources
> ----------------------------------------------------------------------------
>
>                 Key: OSLCCORE-86
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-86
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>          Components: TRS
>            Reporter: James Amsden
>            Assignee: James Amsden
>
> A TRS defines a base of member resources and a change log of creation, deletion or modification change events. The member and changed elements are URLs to the resources, the TRS does not contain any data from the resources themselves. 
> A TRS change event can include a TRS Patch element that provides the changed property values without requiring the TRS consumer to do an additional GET on the resource. 
> However in most cases, a TRS consumer that needs actual resource data from base or changed members of a TRS will need to do individual GETs on each of the resources in order to establish initial copies, or update existing copies.
> This can be a very inefficient and time consuming process for TRS resources that have a large number of rapidly changing members.
> There is a need to provide a more efficient way of getting information from more than one tracked resource at a time so the GETs can be batched together and included inline in a resource.



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