viska
SIP framework built in Rust (by Televiska)
futures-rs
Zero-cost asynchronous programming in Rust (by rust-lang)
Our great sponsors
| viska | futures-rs | |
|---|---|---|
| 4 | 11 | |
| 77 | 5,235 | |
| - | 1.1% | |
| 0.0 | 8.4 | |
| about 2 years ago | 27 days ago | |
| Rust | Rust | |
| GNU General Public License v3.0 or later | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.
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.
viska
Posts with mentions or reviews of viska.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-02-01.
-
rsip: A general purpose SIP (types) library
rsip is part of my Rust Voip stack, along with rsip-dns that I have recently been building through viska, a SIP server. SIP protocol is quite tricky to implement, because it's completely P2P so it has some interesting edge cases compared to HTTP which is way more simple. Viska is wip, needed a good SIP library to be productive there, but now that rsip is kinda done, I am gona move back to it :)
-
Something like Asterisk but in Rust?
I noticed this: https://github.com/vasilakisfil/viska I have not looked at it at all :-) It seems to have been updated fairly recently. Looking at the Readme, there is still a fair way to go, but they've made pretty good progress.
-
It's my first day on Rust. Hi, everyone!
i already found someone with a github repo building a SIP server here: https://github.com/vasilakisfil/viska
-
What sort of mature, open-source libraries do you feel Rust should have but currently lacks?
That said, there's this, which looks to be on the road already! https://github.com/vasilakisfil/viska
futures-rs
Posts with mentions or reviews of futures-rs.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-10-19.
-
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
What are some alternatives?
When comparing viska and futures-rs you can also consider the following projects:
rxRust - Rust implementation of Reactive Extensions.
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
rsip-dns - SIP Rust library implementing RFC 3263, implemented on top of rsip
async-std - Async version of the Rust standard library
mun - Source code for the Mun language and runtime.
carboxyl - Functional Reactive Programming library for Rust
pjproject - PJSIP project
mioco - [no longer maintained] Scalable, coroutine-based, fibers/green-threads for Rust. (aka MIO COroutines).
rust-async-coap - A flexible, asynchronous library for using and serving CoAP resources in Rust.
tangle - Deprecated - Use https://github.com/alexcrichton/futures-rs instead
coio-rs - Coroutine I/O for Rust
LiteDB - LiteDB - A .NET NoSQL Document Store in a single data file