From 00058d2592f51189e15a16d20e72edb006a31773 Mon Sep 17 00:00:00 2001 From: Sachandhan Ganesh Date: Thu, 4 Feb 2021 00:50:31 -0800 Subject: [PATCH] fix heading levels in the readme and bump version --- Cargo.lock | 2 +- Cargo.toml | 2 +- README.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/Cargo.lock b/Cargo.lock index 01e4369..b4a3154 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -257,7 +257,7 @@ dependencies = [ [[package]] name = "connect" -version = "0.0.4" +version = "0.0.5" dependencies = [ "anyhow", "async-channel", diff --git a/Cargo.toml b/Cargo.toml index 55ce619..c488d92 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "connect" -version = "0.0.4" +version = "0.0.5" edition = "2018" authors = ["Sachandhan Ganesh "] description = "message queue abstraction over async network streams" diff --git a/README.md b/README.md index 4c6a834..aedb3e7 100644 --- a/README.md +++ b/README.md @@ -9,14 +9,14 @@ the problem of reliable, fault-tolerant message delivery over byte-streams. By u queue abstraction, crate users can focus on core application logic and leave the low-level networking and message-queue guarantees to the abstraction. -# Protobuf +## Protobuf This crate relies on the use of [Protocol Buffers](https://developers.google.com/protocol-buffers) due to it being widely adopted and industry-proven. All messages are Protobuf messages that are packed into a Protobuf `Any` type and then sent over the wire. Message recipients must decide what Protobuf message type it is, and correspondingly unpack the `Any` into a particular message type. -# Examples +## Examples Please use the [examples](https://github.com/sachanganesh/connect-rs/tree/main/examples) provided to help understand crate usage. -- 2.44.0