> For the complete documentation index, see [llms.txt](https://use.temporal.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://use.temporal.xyz/nozomi/transaction-submission-quic.md). # QUIC Client Low-overhead QUIC submission for workloads that cannot hold a persistent connection open. Nozomi provides a native QUIC client for submitting transactions: [**github.com/temporalxyz/nozomi-quic-client →**](https://github.com/temporalxyz/nozomi-quic-client) ## When to Use It QUIC is **not** faster than the HTTP endpoints when you keep a warm connection open. Over a persistent, reused TCP connection, [Batch Send](/nozomi/batch-send.md) over a direct `http://` endpoint is the lowest-latency path (see [Regions & Endpoints → Choosing a submission method](/nozomi/endpoints.md#choosing-a-submission-method)). QUIC is useful for a **specific case**: workloads that **cannot hold a single connection open** and have to re-establish a connection frequently. QUIC's connection setup (including session resumption) is cheaper than repeatedly completing a fresh TCP + TLS handshake, so you pay less latency per reconnect. Use QUIC when: * You cannot maintain one long-lived, warm connection to a region. * Your process is short-lived, serverless, or otherwise reconnects often. * Network conditions force frequent reconnection. If you can keep a connection open, prefer Batch Send or API v2 over a direct `http://` endpoint instead, and use [TCP Keep-Alive](/nozomi/keeping-your-tcp-connection-alive.md) to keep it warm. ## Notes * The transport you choose does **not** change your priority in Nozomi's queue: priority is driven by your [tip](/nozomi/tipping-and-faq.md), not by QUIC vs HTTP. * Like API v2 and Batch Send, QUIC submission does **not** return a transaction signature. Compute and track the signature client-side before submitting. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://use.temporal.xyz/nozomi/transaction-submission-quic.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.