[Access] Unify subscription id with client message id #6847
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From commit message:
From now on, we use only 1 id in request/response messages. This id is called
subscription_id
.A client may provide
subscription_id
insubscribe
request. If client does not provide it, we generate it ourselves.Clients that use browsers or other async environments may use
subscription_id
to correlate response messages with the request ones.subscription_id
is used in all messages related to subscription.I also removed
success
field from a response. We includesubscription_id
field in a resposne in case of OK response.In case of error response, we include
error
field.Closes #6845