ec963a6e71
The previous implementation used a futures_cpupool for executing blocking juniper operations. This pool comes in addition to the thread pool started by hyper through tokio for executing hyper's futures. This patch uses tokio::blocking to perform the blocking juniper operations while re-using the same thread pool as hyper, which simplifies the API.
29 lines
697 B
TOML
29 lines
697 B
TOML
[package]
|
|
name = "juniper_hyper"
|
|
version = "0.1.0"
|
|
authors = ["Damir Vandic <info@dvic.io>"]
|
|
description = "Juniper GraphQL integration with Hyper"
|
|
license = "BSD-2-Clause"
|
|
documentation = "https://docs.rs/juniper_hyper"
|
|
repository = "https://github.com/graphql-rust/juniper"
|
|
|
|
[dependencies]
|
|
serde = "1.0"
|
|
serde_json = "1.0"
|
|
serde_derive = "1.0"
|
|
url = "1.7"
|
|
juniper = { version = ">=0.9, 0.10.0" , default-features = false, path = "../juniper"}
|
|
|
|
futures = "0.1"
|
|
tokio = "0.1.8"
|
|
hyper = "0.12"
|
|
tokio-threadpool = "0.1.7"
|
|
|
|
[dev-dependencies]
|
|
pretty_env_logger = "0.2"
|
|
reqwest = "0.9"
|
|
|
|
[dev-dependencies.juniper]
|
|
version = "0.10.0"
|
|
features = ["expose-test-schema", "serde_json"]
|
|
path = "../juniper"
|