Mark Mandel
Mark Mandel
> The other thought I had too was it might be worth doing benchmarks with multiple udp clients (maybe more than current cpu on the machine?) and multiple servers, and...
Context: > If the filter traits were moved to another crate, filters could be defined in separate crates and loaded by Quilkin at runtime. That would be much more reasonable...
There are lots of use cases for being able to send packets from a Filter, or something similar, e.g. - DTLS/Encryption that requires a handshake - Sending regular packets to...
It has come up in discussion that it might be optimal to have separate traits for Content Filtering/Modifications, and also for Content Routing. Right now, they are a single Filter...
Looking at this example, and upcoming refactoring to API surfaces, I think it would be good to compile this example and make sure the code is not broken in CI...
Just noticed that godot implemented DTLS into their UDP stack: https://godotengine.org/article/dtls-report-1 https://godotengine.org/article/enet-dtls-encryption From initial review, DTLS gives us encryption, without the overarching of UDP reliability layer that Quic has. That...
This is a placeholder issue to put links for various libraries, ideas and research into encryption for UDP.
Be able to have a filter that is processed Asynchronously. This wouldn't have the ability to block, or route requests, but would allow for processing and parsing of packets not...
I tend to use [`cargo-workspaces`](https://github.com/pksunkara/cargo-workspaces) which has one line commands for syncing the version and publishing across crates in the workspace. _Originally posted by @XAMPPRocky in https://github.com/googleforgames/quilkin/pull/252#discussion_r633209100_ Looks like this...
Right now we use the [prometheus](https://crates.io/crates/prometheus) for metric capture and exposure. OpenTelemetry is a project to watch as an OSS standard for both metrics and telemetry data, with the ability...