Crates.io | sctp-sys |
lib.rs | sctp-sys |
version | 0.0.8 |
source | src |
created_at | 2015-07-25 09:50:23.932243 |
updated_at | 2024-09-23 14:44:57.277783 |
description | Binding to libsctp for linux, and SctpDrv for windows. SctpDrv binding is experimental |
homepage | |
repository | https://github.com/phsym/sctp-sys |
max_upload_size | |
id | 2674 |
size | 41,536 |
Rust bindings to native sctp library. Under linux, libsctp is used and under windows, SctpDrv is used. However, SctpDrv is not really stable, and some BSOD cases have been reported. Thus, you should not use windows SCTP in production environment, but it still may be usefull for development.
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.
Building in linux requires the libsctp usually provided by lksctp-tools development package.
Building in windows requires the SctpDrv driver to be installed, and the file libsctpsp.dll should be stored in a place where cargo can find it.
MAC OS is not supported. Or maybe it is, I don't even know if it's supported and I don't have the required hardware to verify. Any contribution would be welcome.
SctpDrv is not stable, especially in Windows 7 for which BSOD have been reported multiple times, and issues have not been fixed for years. I got a BSOD on my Windows 7 SP1 (64 bits) each time I try to connect a socket. So I can't go further in any kind of validation under windows. When I get more time, I'll try it on other windows versions. Consequently, using SCTP in windows environment should be avoided as much as possible.