[OASIS Issue Tracker] (OSLCCORE-167) Downgrade TRS Server requirements on the TRS Resource HTTP endpoints

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

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

Andrii Berezovskyi commented on OSLCCORE-167:
---------------------------------------------

I would disagree with making conditional GETs a MAY, the rest is OK.

Rationale: when the TRS Base is updated, a TRS Server has to go over to the new TRS Base and fetch every resource linked from it (if it lost the cutoff event). It would be very useful to make an HTTP GET with header like:

If-Modified-Since: Wed, 21 Oct 2015 07:28:00 GMT

And get

304 Not Modified

Instead of a full searialisation in one of the RDF formats. 

> Downgrade TRS Server requirements on the TRS Resource HTTP endpoints 
> ---------------------------------------------------------------------
>
>                 Key: OSLCCORE-167
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-167
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>            Reporter: Andrii Berezovskyi
>            Assignee: Axel Reichwein
>
> Current spec draft reads:
> The TRS Server should support ETags, caching, and conditional GETs for Tracked Resources.



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