Source: dzone.com
An Introduction to RSocketCategory: Data
RSocket is a new communication protocol that promises to solve the issues we have with HTTP, and together with that, it might also simplify the way we design and build distributed systems and microservices.
This blog is the first in a series that covers RSocket, a new reactive communication protocol.
Let's assume that the transport protocol is TCP, then the SETUP frame looks like this if resumption is not in use: TCP has no framing, so the first 24 bits (3 bytes) indicate the frame length (in this case 0x28 or 40 bytes), then there are 32 bits of stream ID, 0x00000000 since the frame is associated with the connection.
The response frame is of the same length, but the type is now PAYLOAD frame with an identifier of 0x0A.
This type of interaction cannot be achieved by HTTP since HTTP, by default, has a response, and even if the requester ignores the response, it is sent and processed by both peers.
This blog is the first in a series that covers RSocket, a new reactive communication protocol.
Let's assume that the transport protocol is TCP, then the SETUP frame looks like this if resumption is not in use: TCP has no framing, so the first 24 bits (3 bytes) indicate the frame length (in this case 0x28 or 40 bytes), then there are 32 bits of stream ID, 0x00000000 since the frame is associated with the connection.
The response frame is of the same length, but the type is now PAYLOAD frame with an identifier of 0x0A.
This type of interaction cannot be achieved by HTTP since HTTP, by default, has a response, and even if the requester ignores the response, it is sent and processed by both peers.
Related Articles
Community Partners
DevOps Careers