Hi Lucas,

This is also the way this projected started: People asked me if something like it exists and after saying no again and again, I realized the need for it, especially as the QUIC Implementations wiki page on Github (https://github.com/quicwg/base-drafts/wiki/Implementations) is also quite outdated and not really extensible.

Considering the pull model: I have not yet thought about that, but that's a great idea, thank you! I already have some nice ideas what could be possible, so I opened an issue (https://github.com/MPK1/quic-explorer/issues/5) and will add some proposals soon.

Marcel

Am 18.07.24 um 19:29 schrieb Lucas Pardue:
Hi Marcel,

Thank you for sharing. I seem to some chatter about how nice it would be to have such a tool to manage this sort of thing in a more automated or structured way but people are, as always, quite busy. So it's great to see efforts being made.

One thought I'd had previously is that it would be nice to define a structured data format and have such a service pull the information from projects where possible. I.e. is the Cloudflare quiche project could host it's own JSON file on Github and then anyone, such as quic-explorer.net could consume it.

Have you considered such an optional pull model?

Cheers
Lucas

On Thu, Jul 18, 2024, at 17:57, Marcel Kempf wrote:
Dear fellow QUIC Enthusiasts,

I would like to share a small side project of mine aimed at helping
developers and researchers find the right QUIC library for their
projects. With numerous QUIC implementations available, choosing the
most suitable one can be challenging, especially if you need support for
specific extensions or implementation details like a specific congestion
control algorithm.

QUIC Explorer addresses this by providing a searchable database of
implementations. It allows users to search and filter QUIC
implementations based on various criteria such as support for extensions
or specific implementation details. The data is stored as JSON on
GitHub, enabling community contributions to keep the information current
and accurate. Each piece of information includes a source (e.g., a link
to the relevant source code) and a "valid as of" field to indicate if
the information might be outdated. The website is built and deployed
using GitHub Actions on every commit to the main branch.

https://quic-explorer.net
https://github.com/MPK1/quic-explorer

Any feedback or suggestions to improve the platform is highly
appreciated. Contributions to the GitHub repository are also very
welcome! Feel free to add information about your favorite implementation
or suggest new features you’re missing. To make contributions easier,
I’ve provided a small (albeit ugly but functional) Python script to add
information to the JSON files more conveniently.

I hope QUIC Explorer will be a helpful resource for anyone involved with
QUIC, whether you're developing applications, conducting research, or
exploring the protocol.

Best regards,

Marcel


P.S.: I am part of the Chair of Network Architectures and Services at
the Technical University of Munich and actively involved in our research
covering QUIC, different implementations and their specifics:
https://net.in.tum.de/projects/quic/

Reply via email to