Skip to content

Commit

Permalink
docs: add upgrade advice around new transport parameters
Browse files Browse the repository at this point in the history
  • Loading branch information
@andrewbonney
andrewbonney committed Jun 12, 2019
1 parent 9808171 commit 5c0236c
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions docs/5.0. Upgrade Path.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,8 @@ Implementers of the Connection Management API must support at least one API vers

Where a transport type is added in a new version of the Connection Management API specification, earlier versioned APIs must not list any Senders or Receivers which make use of this new transport type.

Where new transport parameters are added to a pre-existing transport type in a new version of the Connection Management API, earlier versioned APIs must not list these parameters. New transport parameters should be defined such that a request which omits them can proceed without error. This ensures that servers implementing multiple versions of the Connection Management API can continue to process earlier versioned requests successfully.

Connection Management APIs are not required to provide for forwards compatibility as it may be impossible to generate data for new attributes in schemas.

## Requirements for Connection Management clients
Expand Down

0 comments on commit 5c0236c

Please sign in to comment.