RSocket is an application protocol providing Reactive Streams semantics over an asynchronous, binary boundary.

It enables the following symmetric interaction models via async message passing over a single connection:

• request/response (stream of 1)
• request/stream (finite/infinite stream of many)
• fire-and-forget (no response)
• channel (bi-directional streams)

It also supports connection resumption to allow resuming long-lived streams across different transport connections. This is particularly useful for mobile<->server communication when network connections drop, switch, and reconnect frequently.

Artifacts include:

• RSocket Protocol
• Protocol Extensions
  • Well-known MIME Types
  • Stream Data MIME Types Definition
  • Composite Metadata
  • Routing
  • Tracing (Zipkin)
  • Authentication
• Motivation for creating this protocol
• Frequently Asked Questions

More information and links to various implementations can be found at http://rsocket.io

For bugs, questions and discussions please use the Github Issues.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.