rust-server
gRPC
rust-server | gRPC | |
---|---|---|
14 | 201 | |
81 | 40,775 | |
- | 0.6% | |
6.0 | 9.9 | |
about 1 month ago | 3 days ago | |
Rust | C++ | |
GNU Affero General Public License v3.0 | Apache License 2.0 |
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.
rust-server
-
DCS scripts to extract aircraft position to a third party application.
You can use DCS-gRPC unit stream
-
DCS Code Injector available for download. Made a video about this a while ago and people expressed interest so I cleaned it up a bit. You can grab it from my Github now if you want to take it for a spin. Link to the video is in there as well.
Installing DCS-gRPC is like most plugins. Instructions in the README https://github.com/DCS-gRPC/rust-server/blob/main/README.md
-
DCS-gRPC 0.7.0 Released!
This provides a wide variety of voices and providers that can be used together inside a single mission. We have also added some new APIs. See the release link at the bottom for a full listing. A summary page that shows what APIs have been implemented so far can be viewed here.
-
OverlordBot Mid-Year Update
Spent a lot of time working on the DCS-gRPC project with others and also making sample applications for it.
This has been released and OverlordBot now uses the DCS-gRPC project as its datasource for everything going on in the mission. At some point the vestigially supported Tacview code will be removed.
-
DCS-gRPC 0.4.0 Released!
See https://github.com/DCS-gRPC/rust-server/releases/tag/0.5.0 for download and full release information.
We have also created a summary page that shows what APIs have been implemented so far which can be viewed here.
-
Injecting events into running missions externally
You might want to checkout DCS-gRPC https://github.com/DCS-gRPC/rust-server/wiki
-
DCS-gRPC 0.3.0 Released
DCS-gRPC has a number of sample applications available. For information on the sample applications have a look at https://github.com/DCS-gRPC/rust-server/wiki/Sample-Applications
-
OverlordBot Roadmap
OverlordBot is a hobby project developed by one person in my spare time when I am not playing DCS or other games and not doing those annoying adult things need to do. Therefore the amount of work that can be done in terms of new features is limited when I also have to deal with onboarding new servers, debugging issues, code refactoring and other ancilliary work that comes with running a production application. As well as this I also work on other projects such as DCS-gRPC and its sample applications which also competes for my time.
gRPC
-
Golang: out-of-box backpressure handling with gRPC, proven by a Grafana dashboard
gRPC, built on HTTP/2, inherently supports flow control. The server can push updates, but it must also respect flow control signals from the client, ensuring that it doesn't send data faster than what the client can handle.
-
Reverse Engineering Protobuf Definitions from Compiled Binaries
Yes, grpc_cli tool uses essentially the same mechanism except implemented as a grpc service rather than as a stubby service. The basic principle of both is implementing the C++ proto library's DescriptorDatabase interface with cached recursive queries of (usually) the server's compiled in FileDescriptorProtos.
See also https://github.com/grpc/grpc/blob/master/doc/server-reflecti...
The primary difference between what grpc does and what stubby does is that grpc uses a stream to ensure that the reflection requests all go to the same server to avoid incompatible version skew and duplicate proto transmissions. With that said, in practice version skew is rarely a problem for grpc_cli style "issue a single RPC" usecases: even if requests do go to two or more different versions of a binary that might have incompatible proto graphs, it is very common for the request and response and RPC to all be in the same proto file so you only need to make one RPC in the first place unless you're using an extension mechanism like proto2 extensions or google.protobuf.Any.
-
Delving Deeper: Enriching Microservices with Golang with CloudWeGo
While gRPC and Apache Thrift have served the microservice architecture well, CloudWeGo's advanced features and performance metrics set it apart as a promising open source solution for the future.
-
gRPC Name Resolution & Load Balancing on Kubernetes: Everything you need to know (and probably a bit more)
The loadBalancingConfig is what we use in order to decide which policy to go for (round_robin in this case). This JSON representation is based on a protobuf message, then why does the name resolver returns it in the JSON format? The main reason is that loadBalancingConfig is a oneof field inside the proto message and so it can not contain values unknown to the gRPC if used in the proto format. The JSON representation does not have this requirement so we can use a custom loadBalancingConfig .
-
Dart on the Server: Exploring Server-Side Dart Technologies in 2024
The Dart implementation of gRPC which puts mobile and HTTP/2 first. It's built and maintained by the Dart team. gRPC is a high-performance RPC (remote procedure call) framework that is optimized for efficient data transfer.
- Usando Spring Boot RestClient
-
How to Build & Deploy Scalable Microservices with NodeJS, TypeScript and Docker || A Comprehesive Guide
gRPC is a high-performance, open-source RPC (Remote Procedure Call) framework initially developed by Google. It uses Protocol Buffers for serialization and supports bidirectional streaming.
-
Actual SSH over HTTPS
In general, tunneling through HTTP2 turns out to be a great choice. There is a RPC protocol built on top of HTTP2: gRPC[1].
This is because HTTP2 is great at exploiting a TCP connection to transmit and receive multiple data structures concurrently - multiplexing.
There may not be a reason to use HTTP3 however, as QUIC already provides multiplexing.
I expect that in the future most communications will be over encrypted HTTP2 and QUIC simply because middleware creators can not resist to discriminate.
[1] <https://grpc.io>
-
Why gRPC is not natively supported by Browsers
Even in the https://grpc.io blog says this
-
SGSG (Svelte + Go + SQLite + gRPC) - open source application
gRPC
What are some alternatives?
lso - LSO bot for DCS using DCS-gRPC
ZeroMQ - ZeroMQ core engine in C++, implements ZMTP/3.1
TTS - πΈπ¬ - a deep learning toolkit for Text-to-Speech, battle-tested in research and production
Apache Thrift - Apache Thrift
srs-bot
Cap'n Proto - Cap'n Proto serialization/RPC system - core tools and C++ library
DATIS - DCS World Automatic Terminal Information Service (ATIS) broadcasted through Simple Radio Standalone (SRS)
zeroRPC - zerorpc for python
dct - Dynamic Campaign Tools - mission scripting framework for large persistent DCS missions
rpclib - rpclib is a modern C++ msgpack-RPC server and client library
dcs_code_injector - Application to interact with Digital Combat Simulator while a mission is running
nanomsg - nanomsg library