rust-lightning/lightning-net-tokio/Cargo.toml

[package]
name = "lightning-net-tokio"
version = "0.0.117-alpha2"
authors = ["Matt Corallo"]
license = "MIT OR Apache-2.0"
repository = "https://github.com/lightningdevkit/rust-lightning/"
description = """
Implementation of the rust-lightning network stack using Tokio.
For Rust-Lightning clients which wish to make direct connections to Lightning P2P nodes, this is a simple alternative to implementing the required network stack, especially for those already using Tokio.
"""
edition = "2018"

[package.metadata.docs.rs]
all-features = true
rustdoc-args = ["--cfg", "docsrs"]

[dependencies]
bitcoin = "0.29.0"
lightning = { version = "0.0.117-alpha2", path = "../lightning" }
tokio = { version = "1.0", features = [ "rt", "sync", "net", "time" ] }

[dev-dependencies]
tokio = { version = "1.14", features = [ "macros", "rt", "rt-multi-thread", "sync", "net", "time" ] }
lightning = { version = "0.0.117-alpha2", path = "../lightning", features = ["_test_utils"] }
Add subcrate that implements network socket handling with Tokio This is still pretty raw and ist mostly just a straight move from rust-lightning-bitcoinrpc, but first step is to get it there, second is to actually make it actually safe to use. 2019-06-01 13:02:31 +02:00			`[package]`
			`name = "lightning-net-tokio"`
Bump versions to 0.0.117-alpha2/invoice 0.25.0-alpha2 2023-09-26 22:21:08 +02:00			`version = "0.0.117-alpha2"`
Add subcrate that implements network socket handling with Tokio This is still pretty raw and ist mostly just a straight move from rust-lightning-bitcoinrpc, but first step is to get it there, second is to actually make it actually safe to use. 2019-06-01 13:02:31 +02:00			`authors = ["Matt Corallo"]`
Update licenses and add missing fields in Cargo.toml files 2021-03-09 22:51:14 +01:00			`license = "MIT OR Apache-2.0"`
update repo name to use lightningdevkit 2021-12-27 04:53:16 +01:00			`repository = "https://github.com/lightningdevkit/rust-lightning/"`
Add subcrate that implements network socket handling with Tokio This is still pretty raw and ist mostly just a straight move from rust-lightning-bitcoinrpc, but first step is to get it there, second is to actually make it actually safe to use. 2019-06-01 13:02:31 +02:00			`description = """`
			`Implementation of the rust-lightning network stack using Tokio.`
Fix typo in lightning-net-tokio crate description. 2020-02-04 00:47:38 +01:00			`For Rust-Lightning clients which wish to make direct connections to Lightning P2P nodes, this is a simple alternative to implementing the required network stack, especially for those already using Tokio.`
Add subcrate that implements network socket handling with Tokio This is still pretty raw and ist mostly just a straight move from rust-lightning-bitcoinrpc, but first step is to get it there, second is to actually make it actually safe to use. 2019-06-01 13:02:31 +02:00			`"""`
Update licenses and add missing fields in Cargo.toml files 2021-03-09 22:51:14 +01:00			`edition = "2018"`
Add subcrate that implements network socket handling with Tokio This is still pretty raw and ist mostly just a straight move from rust-lightning-bitcoinrpc, but first step is to get it there, second is to actually make it actually safe to use. 2019-06-01 13:02:31 +02:00
Generate docs with features for docs.rs Enable generating docs using --all-features or --features="std" where applicable. Additionally, use doc_auto_cfg to tag items requiring a feature. https://doc.rust-lang.org/nightly/rustdoc/unstable-features.html#doc_auto_cfg-automatically-generate-doccfg This requires building with nightly, which is what is used by docs.rs. https://docs.rs/about/builds To test locally, use: RUSTDOCFLAGS="--cfg docsrs" cargo +nightly doc ... 2022-02-12 05:22:20 +01:00			`[package.metadata.docs.rs]`
			`all-features = true`
			`rustdoc-args = ["--cfg", "docsrs"]`

Add subcrate that implements network socket handling with Tokio This is still pretty raw and ist mostly just a straight move from rust-lightning-bitcoinrpc, but first step is to get it there, second is to actually make it actually safe to use. 2019-06-01 13:02:31 +02:00			`[dependencies]`
Update bitcoin crate to 0.29.0 2022-08-09 17:39:51 +02:00			`bitcoin = "0.29.0"`
Bump versions to 0.0.117-alpha2/invoice 0.25.0-alpha2 2023-09-26 22:21:08 +02:00			`lightning = { version = "0.0.117-alpha2", path = "../lightning" }`
Drop dep `tokio`'s `io-util` feat as it broke MSRV and isn't useful We use `tokio`'s `io-util` feature to provide the `Async{Read,Write}Ext` traits, which allow us to simply launch a read future or `poll_write` directly as well as `split` the `TcpStream` into a read/write half. However, these traits aren't actually doing much for us - they are really just wrapping the `readable` future (which we can trivially use ourselves) and `poll_write` isn't doing anything for us that `poll_write_ready` can't. Similarly, the split logic is actually just `Arc`ing the `TcpStream` and busy-waiting when an operation is busy to prevent concurrent reads/writes. However, there's no reason to prevent concurrent access at the stream level - we aren't ever concurrently writing or reading (though we may concurrently read and write, which is fine). Worse, the `io-util` feature broke MSRV (though they're likely to fix this upstream) and carries two additional dependencies (only one on the latest upstream tokio). Thus, we simply drop the dependency here. Fixes #2527. 2023-08-28 20:39:04 +02:00			`tokio = { version = "1.0", features = [ "rt", "sync", "net", "time" ] }`
Rewrite lightning-net-tokio using async/await and tokio 0.2 This is a rather major rewrite, using async/await and tokio 0.2, which cleans up the code a ton as well as adds significantly to readability. 2020-02-01 18:27:30 +01:00
			`[dev-dependencies]`
Drop dep `tokio`'s `io-util` feat as it broke MSRV and isn't useful We use `tokio`'s `io-util` feature to provide the `Async{Read,Write}Ext` traits, which allow us to simply launch a read future or `poll_write` directly as well as `split` the `TcpStream` into a read/write half. However, these traits aren't actually doing much for us - they are really just wrapping the `readable` future (which we can trivially use ourselves) and `poll_write` isn't doing anything for us that `poll_write_ready` can't. Similarly, the split logic is actually just `Arc`ing the `TcpStream` and busy-waiting when an operation is busy to prevent concurrent reads/writes. However, there's no reason to prevent concurrent access at the stream level - we aren't ever concurrently writing or reading (though we may concurrently read and write, which is fine). Worse, the `io-util` feature broke MSRV (though they're likely to fix this upstream) and carries two additional dependencies (only one on the latest upstream tokio). Thus, we simply drop the dependency here. Fixes #2527. 2023-08-28 20:39:04 +02:00			`tokio = { version = "1.14", features = [ "macros", "rt", "rt-multi-thread", "sync", "net", "time" ] }`
Bump versions to 0.0.117-alpha2/invoice 0.25.0-alpha2 2023-09-26 22:21:08 +02:00			`lightning = { version = "0.0.117-alpha2", path = "../lightning", features = ["_test_utils"] }`