Create subdir for tower crate (#182)

This commit is contained in:
Carl Lerche 2019-03-06 07:54:39 -08:00 committed by GitHub
parent fb01af2ad9
commit 794aa44c4b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 34 additions and 25 deletions

View File

@ -1,31 +1,7 @@
[package]
name = "tower"
version = "0.1.0"
authors = ["Carl Lerche <me@carllerche.com>"]
license = "MIT"
readme = "README.md"
repository = "https://github.com/tower-rs/tower"
publish = false
description = """
Tower is a library of modular and reusable components for building robust
clients and servers.
"""
categories = ["asynchronous", "network-programming"]
keywords = ["io", "async", "non-blocking", "futures", "service"]
[dev-dependencies]
tower-service = { version = "0.2", path = "tower-service" }
tower-util = { version = "0.1", path = "tower-util" }
futures = "0.1"
log = "0.4.1"
env_logger = { version = "0.5.3", default-features = false }
tokio-timer = "0.1"
futures-cpupool = "0.1"
[workspace]
members = [
"./",
"tower",
"tower-balance",
"tower-buffer",
"tower-discover",

23
tower/Cargo.toml Normal file
View File

@ -0,0 +1,23 @@
[package]
name = "tower"
version = "0.1.0"
authors = ["Carl Lerche <me@carllerche.com>"]
license = "MIT"
readme = "README.md"
repository = "https://github.com/tower-rs/tower"
publish = false
description = """
Tower is a library of modular and reusable components for building robust
clients and servers.
"""
categories = ["asynchronous", "network-programming"]
keywords = ["io", "async", "non-blocking", "futures", "service"]
[dev-dependencies]
tower-service = { version = "0.2", path = "../tower-service" }
tower-util = { version = "0.1", path = "../tower-util" }
futures = "0.1"
log = "0.4.1"
env_logger = { version = "0.5.3", default-features = false }
tokio-timer = "0.1"
futures-cpupool = "0.1"

10
tower/README.md Normal file
View File

@ -0,0 +1,10 @@
# Tower
Tower is a library of modular and reusable components for building robust
networking clients and servers.
## Overview
Tower aims to make it as easy as possible to build robust networking clients and
servers. It is protocol agnostic, but is designed around a request / response
pattern. If your protocol is entirely stream based, Tower may not be a good fit.