Remove the jsr-356 Transport. #90
Merged
Conversation
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
Despite being functional, we don't use the transport and we don't plan to in a near future.
Member
Author
|
Merging myself since it isn't anything contentious. |
ilayaperumalg
pushed a commit
to ilayaperumalg/rsocket-java
that referenced
this pull request
Dec 26, 2017
* Introducing default mime type for metadata. As per discussion in issue rsocket#89, this change proposes a default mime-type for metadata payloads. Existing `Schema.md` is replaced by this new `MimeTypes.md` document which elaborates this new mime type. * Incorporating review comments. - Removed the custom encoding and using CBOR. - Text formatting. - Language correction for optional encoding. * Updates the mimetype name Modified the name of the mimetype to "application/x.reactivesocket.meta+cbor" since it is a specific schema for metadata and not just cbor. * Update Protocol.md * Update Protocol.md
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Despite being functional, we don't use the transport and
we don't plan to in a near future.