Martin Duke

The design team explicitly punted the incompatible VN issue because it was hard and not urgent. But as Mike said, any two QUIC versions are absolutely negotiable, though it might...

> @martinduke which design team are you referring to? It's a shorthand for you, me and @martinthomson. It's probably too grandiose of a word to describe what that was. Apologies.

The v2 draft currently says: > QUIC version 2 is not intended to deprecate version 1. Endpoints that support version 2 might continue support for version 1 to maximize compatibility...

I had envisioned a link to the beginning of the thread, but the canned search example you propose is at least a 95% solution, and arguably better. If much easier,...

SGTM

It looks the like we can figure out the API simply by working through the autocomplete https://registry.wapm.io/graphql Is there really nowhere where this is written down for public consumption?

> > Is there really nowhere where this is written down for public consumption? > > We haven't written anything down, but we can write it if it's useful. What...

Thanks, that's very helpful!

I encourage this group to not reinvent the wheel that is being forged in the IETF Transport Services working group: https://datatracker.ietf.org/wg/taps/documents/

If you want a writeup, the TAPS architecture draft is a good place to start: https://www.ietf.org/id/draft-ietf-taps-arch-08.html Some of the other documents in there show what capabilities the API would have...