Edge Rewrite
// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a21ad0b61ab0d685

Jump to content

RSocket

From Wikipedia, the free encyclopedia
RSocket
Release26 October 2015; 10 years ago (2015-10-26)
Written inJava, JavaScript, Kotlin, C#, Go, C++, Python
TypeReactive Streams networking
LicenseApache License
Websitersocket.io
Repositorygithub.com/rsocket

RSocket is an application protocol initially developed by Netflix,[1] that supports Reactive Streams. The motivation behind its development was to replace HTTP, which is inefficient for many tasks such as microservices communication, with a protocol that has less overhead.[2]

Protocol

[edit]

RSocket is a binary protocol for use on byte stream transports such as TCP and WebSocket. It enables the following symmetric interaction models via async message passing over a single connection:

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

It supports session 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.

References

[edit]
  1. Monkiewicz, Łukasz (June 4, 2017). "A summary of Code Europe 2017 in Warsaw". lmonkiewicz.com. Retrieved May 7, 2017.
  2. Christensen, Ben (Apr 3, 2017). "Motivations". github.com. Retrieved May 7, 2017.
[edit]