Feature: Allow switching between batched and non-batched transport based on request
See original GitHub issueBased on this conversation: https://apollographql.slack.com/archives/C11QBB84R/p1495471281173263
It would be great to have a new NetworkInterface type that uses a batch transport by default but allows you to force a single request if you don’t want it to batch. This is useful since it’s possible for automatic batching to hold up an entire page because fast important queries are batched with slow unimportant ones, which end up blocking all requests on the slowest query
A possible implementation / design would be a new HTTPHybridNetworkInterface
(or a better name if people have one) that would wrap a HTTPFetchNetworkInterface
and a HTTPBatchNetworkInterface
and route requests to one or the other based on a property of the request
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Batching Client GraphQL Queries
Batching is the process of taking a group of requests, combining them into one, and making a single request with the same data...
Read more >Jira notifications piling up in the mail queue due to SMTP ...
All notification emails from Jira (batched notifications, non-batched notifications, customer notifications) are piling up in the queue and ...
Read more >Integrating NVIDIA Triton Inference Server with Kaldi ASR
Dynamic batcher: Inference requests can be combined by the server, so that a batch ... this requires a context switch between batches (d)....
Read more >JSON 2.0 batch - Google Groups
Hi, I saw the batch in the new proposed specification. And I'm wondering: what is the benefit? It seems, the server is not...
Read more >Communications Programming Concepts - RPC Features
The features of Remote Procedure Call (RPC) include batching calls, ... Callback procedures permit a server to become a client and make an...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
https://github.com/apollographql/core-docs/pull/300 there you go
Yep, that’s exactly what I ended up doing and it works for us.
For other folks who want to do something similar, we’re basically doing this: