Skip to content
This repository was archived by the owner on Aug 30, 2022. It is now read-only.

Implemented a Proposal for Automatic Content Negation and ETag Support (issues #3 and #5) - #17

Open
martinlanter wants to merge 3 commits into
eclipse-archived:masterfrom
martinlanter:accept-and-etag
Open

Implemented a Proposal for Automatic Content Negation and ETag Support (issues #3 and #5)#17
martinlanter wants to merge 3 commits into
eclipse-archived:masterfrom
martinlanter:accept-and-etag

Conversation

@martinlanter

Copy link
Copy Markdown
Contributor

This is a proposal how to make it easier for the developer of a resource to use ETags and to define which content formats the resources support.

…rface ETagSupport

and a default implementation ETagDefaultSupport and JUnit tests. A
CoapResource now has a ETagSupport object that generates ETags if
required. If an incoming request has ETags, the resource automatically
validates them against the current value in the ETagSupport object and
responds with a 2.03 (Valid) if an ETag matches.
…Added an interface

AcceptSupport and a default implementation AcceptDefaultSupport and a
JUnit test. A CoapResource now has an AcceptSupport object. If a
resource defines some specific formats that are being accepted and the
request asks for another format, the resource automatically responds
with a 4.06.
sbernard31 pushed a commit to sbernard31/californium that referenced this pull request Dec 23, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant