CODEWITHSUNDEEP
grpcquic
Andy N
Andy N

Reputation: 1304

Pushing files over QUIC?

I would like to create a mechanism to allow clients to subscribe to the contents of a blob-storage bucket.

Traditionally (HTTP 1.1) this would involve polling for new items, then issuing a GET requests for each item.

Mechanisms such as gRPC allow responses to be streamed, however that particular mechanism relies on messages being loaded into memory, limiting incoming messages to a few MB.

Does a "push" mechanism exist that would allow a server to transmit larger payloads to clients without requiring the client to request that specific payload?

Upvotes: 0

Views: 660

Answers (1)

Phoenix
Phoenix

Reputation: 1788

I'm assuming that by QUIC you mean HTTP3. HTTP3 is associated with the newly emerging WebTransport API, which allows HTTP3 browser clients to create unidirectional and bidirectional streams with minimal abstraction over the underlying QUIC connection. You could use this to have a HTTP3 web server push files to the client by opening streams within a WebTransport connection, writing some header describing the file to be sent, then writing the rest of the file, then closing that stream.

Upvotes: 1

Related Questions