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-72) TRS should support push-based notification

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

James Amsden updated OSLCCORE-72:

    Component/s: TRS

> TRS should support push-based notification
> ------------------------------------------
>                 Key: OSLCCORE-72
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-72
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Improvement
>          Components: TRS
>            Reporter: David Honey
>            Assignee: James Amsden
> The current TRS design is based on a pull model in which a consumer has to keep polling the TRS to determine whether there are TRS events for tracked resources of interest. There is a tradeoff between the overhead of frequent polling and the latency in which indexed resources may have stale data after the data provider has applied changes and published events. This makes it difficult for the current design to satisfy requirements for a low-latency solution without the overhead of frequent and continuous polling.

This message was sent by Atlassian JIRA

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