spec: Allow REST publisher to publish on behalf of another client#140
Merged
mattheworiordan merged 2 commits intosourcefrom Aug 10, 2016
Merged
spec: Allow REST publisher to publish on behalf of another client#140mattheworiordan merged 2 commits intosourcefrom
mattheworiordan merged 2 commits intosourcefrom
Conversation
Member
|
LGTM |
mattheworiordan
force-pushed
the
connection-key-publishing
branch
from
36732d6 to
b1383eb
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
See https://www.ably.io/documentation/rest/channels-messages#publish-on-behalf
We need to add
connectionKeyto message definition so that REST clients can publish on behalf of other realtime clients.@paddybyers I would like to merge this ASAP as it is a blocker for a customer.