Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fixes #581
- Loading branch information
Showing
1 changed file
with
11 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2b1fcbe
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aren't these backward-compatible techniques?
2b1fcbe
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes are backwards-incompatible; if they were backwards-compatible, you could continue to use the existing URL / media type / header field.
2b1fcbe
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, a new header field can be sent alongside the old one. Same for a new link relation. A new media type might be backwards compatible, depending on who sends it (a server responding might use Accept from the request).
2b1fcbe
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
note that I used the terminology "backwards-compatible changes", not "techniques".