OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


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

James Amsden commented on OSLCCORE-86:
--------------------------------------

We discussed this in the Core TC call today. There was common agreement that this is a significant new feature that would benefit from some research, exploration and prototype solutions before any proposed addition to the TRS spec be adopted. This ensures the TC is standardizing on things that have been proven to satisfy requirements in an implementable way.

We also agreed that this is something the Core TC should take up, and perhaps explore some potential solutions that would be candidates for prototype implementations by existing TRS consumers and providers.

The resulting action is the opening of this issue. 

> 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
>            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)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]