From f5be921aa4c9541ab5079a5c2b563cd38db6961c Mon Sep 17 00:00:00 2001 From: Vincent Batts Date: Tue, 19 Apr 2022 12:33:27 -0400 Subject: [PATCH] PROTOCOL: slight markdown touchup Signed-off-by: Vincent Batts --- PROTOCOL.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/PROTOCOL.md b/PROTOCOL.md index 5475e0be6..12b43f6bd 100644 --- a/PROTOCOL.md +++ b/PROTOCOL.md @@ -103,7 +103,7 @@ interpreted as an empty object. For example, transmitting the number zero as a protobuf message ends up with a data length of zero, but the message is still considered data and should be processed. -#### Data +#### Data Flags | Flag | Name | Description | |------|-----------------|-----------------------------------| @@ -150,8 +150,8 @@ even after it has already completed sending data before the client. | +----------+ | | | - ### Non-Unary State Diagrams + RC: `remote closed` flag RO: `remote open` flag @@ -223,7 +223,7 @@ RO: `remote open` flag | +-----------+ | | | -# RPC +## RPC While this protocol is defined primarily to support Remote Procedure Calls, the protocol does not define the request and response types beyond the messages @@ -232,7 +232,7 @@ definition of request and response which may be used for cross language rpc. All implementations should at least define a request type which support routing by procedure name and a response type which supports call status. -# Version History +## Version History | Version | Features | |---------|---------------------|