~nickbp/tokio-scgi

27198d2b5f4bee397f94bd42c7df6ebdfb873b7e — Nick Parker 2 months ago 18923e7 main
Update repo URL
2 files changed, 4 insertions(+), 4 deletions(-)

M Cargo.toml
M README-CRATES.md
M Cargo.toml => Cargo.toml +2 -2
@@ 1,6 1,6 @@
[package]
name = "tokio-scgi"
version = "0.2.3"
version = "0.2.4"
authors = ["Nick Parker <nick@nickbp.com>"]
license = "MIT"
edition = "2018"


@@ 9,7 9,7 @@ edition = "2018"
# Just avoid that mess and just use a stub README for crate releases that links to the repo.
readme = "README-CRATES.md"
description = "Tokio codec for building and parsing SCGI requests"
repository = "https://github.com/nickbp/tokio-scgi"
repository = "https://sr.ht/~nickbp/tokio-scgi/"
# Per above, leave out the artifacts relating to the main README.
exclude = ["README.md", "images/"]


M README-CRATES.md => README-CRATES.md +2 -2
@@ 4,10 4,10 @@ This is a Rust library which implements support for building [SCGI](https://pyth

SCGI is a [simple and efficient](http://python.ca/scgi/protocol.txt) protocol for communicating between frontend web servers and backend applications over a TCP or local Unix socket. It compares (favorably) to [FastCGI](https://en.wikipedia.org/wiki/FastCGI), another protocol with a similar purpose. This library provides support for writing both SCGI servers and clients in Rust, with support for both TCP and Unix sockets.

For usage information and working client/server examples, see [the project README and repo](https://github.com/nickbp/tokio-scgi).
For usage information and working client/server examples, see [the project README and repo](https://sr.ht/~nickbp/tokio-scgi/).

## async/await

The tokio-scgi 0.2.0 release switches the client/server examples to using async/await. There have been no changes to the SCGI codecs themselves, and they do not require async/await.

Building the examples provided with tokio-scgi 0.2.0 therefore requires Rust 1.39.0 or newer, while the codecs themselves do not. If you regardless want to compile the examples with an older version of Rust, then you can use tokio-scgi 0.1.0, and the codecs themselves will be the same. However any future changes to the codecs will be against the 0.2.0 tree.
Building the examples provided with tokio-scgi 0.2.0+ therefore requires Rust 1.39.0 or newer, while the codecs themselves do not. If you regardless want to compile the examples with an older version of Rust, then you can use tokio-scgi 0.1.0, and the codecs themselves will be the same. However any future changes to the codecs will be against the 0.2.0 tree.