yume/juniper
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
juniper/juniper_hyper/Cargo.toml

31 lines
707 B
TOML
Raw Normal View History

Hyper integration crate (#230) This adds the new integration crate `juniper_hyper`.
2018-09-02 05:02:01 +02:00
[package]
name = "juniper_hyper"
Release juniper_hyper 0.3.0
2019-05-16 19:05:32 -07:00
version = "0.3.0"
Hyper integration crate (#230) This adds the new integration crate `juniper_hyper`.
2018-09-02 05:02:01 +02:00
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"
Refactor code to 2018 edition with 'cargo fix --edition'
2019-04-22 20:37:46 +02:00
edition = "2018"
Hyper integration crate (#230) This adds the new integration crate `juniper_hyper`.
2018-09-02 05:02:01 +02:00
[dependencies]
serde = "1.0"
serde_json = "1.0"
serde_derive = "1.0"
url = "1.7"
Release juniper 0.12.0
2019-05-16 19:03:21 -07:00
juniper = { version = "0.12.0" , default-features = false, path = "../juniper"}
Hyper integration crate (#230) This adds the new integration crate `juniper_hyper`.
2018-09-02 05:02:01 +02:00
futures = "0.1"
Use only a single thread pool for juniper_hyper (#256) 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.
2018-09-30 14:07:44 -04:00
tokio = "0.1.8"
Hyper integration crate (#230) This adds the new integration crate `juniper_hyper`.
2018-09-02 05:02:01 +02:00
hyper = "0.12"
Use only a single thread pool for juniper_hyper (#256) 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.
2018-09-30 14:07:44 -04:00
tokio-threadpool = "0.1.7"
Hyper integration crate (#230) This adds the new integration crate `juniper_hyper`.
2018-09-02 05:02:01 +02:00
[dev-dependencies]
pretty_env_logger = "0.2"
Use only a single thread pool for juniper_hyper (#256) 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.
2018-09-30 14:07:44 -04:00
reqwest = "0.9"
Hyper integration crate (#230) This adds the new integration crate `juniper_hyper`.
2018-09-02 05:02:01 +02:00
[dev-dependencies.juniper]
Release juniper 0.12.0
2019-05-16 19:03:21 -07:00
version = "0.12.0"
Hyper integration crate (#230) This adds the new integration crate `juniper_hyper`.
2018-09-02 05:02:01 +02:00
features = ["expose-test-schema", "serde_json"]
path = "../juniper"
Reference in a new issue Copy permalink