futures-rs
pjproject
futures-rs | pjproject | |
---|---|---|
11 | 7 | |
5,235 | 1,839 | |
0.6% | 1.1% | |
8.4 | 9.0 | |
about 1 month ago | 9 days ago | |
Rust | C | |
Apache License 2.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
futures-rs
-
Which async channel is best?
So this is actually better than true fairness (true fairness would lead to deadlock if a sender is forgotten). It is a pity that the there does not seem to be resources that document this design. There is this old thread where Carl provides some background, but I found it personally a bit hard to follow.
-
Async cancellation: a case study of pub-sub in mini-redis
Is this still true after it switched to using FuturesOrdered?
-
I don't really understand how I'm supposed to use async
Done.
-
Confused about how to use tokio to process a vector in parallel
You can use Streams, which are the async version of Iterators; They aren't stable yet, so you'll have to use a crate such as futures.
-
What crates would you consider essential?
futures
-
How to architect Rust code on Async/Await
For traits, like AsyncRead and AsyncWrite, go with the futures crate.
-
Async Rust in Practice: Performance, Pitfalls, Profiling
Here is the PR: https://github.com/rust-lang/futures-rs/pull/2551
Yield = wake the `waker_ref`. Avoiding the yield would be clone().wake().
That said, "poll immediately" isn't actually a thing nor was it ever a thing except in incorrect implementations.
-
What sort of mature, open-source libraries do you feel Rust should have but currently lacks?
Rust lacks an implementation of ReactiveX. futures/futures-signals seems to be the the ecosystem equivalent but I'm sure there'd be a lot of interest in an actual implementation.
-
Why isn't `rc::Weak<T>` marked `UnwindSafe`when T is `RefUnwindSafe`?
The opposite problem exists as well. Many types are actually unwind safe, but do not get the autotrait. In that case authors would have to manually declare them UnwindSafe. Because this is rarely done, having an API with a trait bound T: UnwindSafe is rarely viable in terms of ergonomics. It now obliges client code to wrap all calls to your API in AssertUnwindSafe which, if they use types from third party libraries, obliges them to assert this is fine. example
-
futures 0.3.9 released with big improvement in compile time
Also, we plan to give users more control in the future. See https://github.com/rust-lang/futures-rs/issues/2207, https://github.com/rust-lang/futures-rs/issues/2295, etc. for this
pjproject
-
Hi, anyone used PJSIP for P2P connectivity (ICE)
Hello, I'm in the process of developing a multiplayer FPS game and recently delved into ICE connectivity (STUN/TURN). Currently, my setup involves a custom matchmaking server in C++, with UDP port handling on the client side through UPnP or a fallback custom relay server. While the current approach works well, I'm exploring options to simplify the project by incorporating existing technologies. I've come across Libjuice and Libpjsip for NAT traversal. Libjuice offers a nice and simple API, but it supports only one person. Hence, I'm considering Libpjsip. I came across their ICE demo script at https://github.com/pjsip/pjproject/blob/master/pjsip-apps/src/samples/icedemo.c and I'm curious about its performance, particularly the pj_ice_strans_sendto2 function. I'm keen to understand how it compares to my current implementation with Berkeley Sockets and whether Libpjsip is a suitable choice for multiplayer P2P games. Any insights or assistance would be highly appreciated. Thanks!
- How to implement video call feature in Native android with kotlin?
-
Something like Asterisk but in Rust?
Things improved a lot thanks to the adoption of the pjsip stack.
-
What sort of mature, open-source libraries do you feel Rust should have but currently lacks?
When I look at stuff like pjsip, I get the impression, it would be huge amount of work. Am I mistaken?
-
Creating new project using PJSIP library in Visual Studio 2015
The first issue I'm facing is I can't find lib folder which is mentioned in Using pjproject libraries for your own application heading in the above-mentioned link. I download the source code from this link.
-
Beaker Browser - An experimental peer-to-peer Web browser.
For client and server, I'm only really familiar with https://www.pjsip.org/. It also comes with a bunch of code for doing phone calls, which really most SIP Stacks were built around. But those parts can just not be used.
-
SIP Phone with GUI on STM32F7
PJSIP (https://github.com/pjsip/pjproject) is used as SIP framework
What are some alternatives?
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
flutter-webrtc - WebRTC plugin for Flutter Mobile/Desktop/Web
async-std - Async version of the Rust standard library
embox - Modular and configurable OS for embedded applications
carboxyl - Functional Reactive Programming library for Rust
freeswitch - FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a versatile software implementation that runs on any commodity hardware. From a Raspberry PI to a multi-core server, FreeSWITCH can unlock the telecommunications potential of any device.
mioco - [no longer maintained] Scalable, coroutine-based, fibers/green-threads for Rust. (aka MIO COroutines).
not-yet-awesome-rust - A curated list of Rust code and resources that do NOT exist yet, but would be beneficial to the Rust community.
tangle - Deprecated - Use https://github.com/alexcrichton/futures-rs instead
tSIP - SIP softphone
coio-rs - Coroutine I/O for Rust
beaker - An experimental peer-to-peer Web browser