You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was exploring a case where we are using @apollo/client/link/batch-http.
In our case, we batched queries that have the same operation name. So we finally with an array of requests in a single HTTP request. Something like that
So, shouldn't we have been catching this case and increasing the timeout based on the number of queries? Because I feeling that we are setting up the timeout per query and in a batched case we are doing more than one so obviously this will take more time.
Maybe we could enable a flag to do that? Currently, we are increasing the timeout manually using the context.
Happy to contribute if it needs it and also hear other thoughts about it. 😊
The text was updated successfully, but these errors were encountered:
I was exploring a case where we are using
@apollo/client/link/batch-http
.In our case, we batched queries that have the same operation name. So we finally with an array of requests in a single HTTP request. Something like that
So, shouldn't we have been catching this case and increasing the timeout based on the number of queries? Because I feeling that we are setting up the timeout per query and in a batched case we are doing more than one so obviously this will take more time.
Maybe we could enable a flag to do that? Currently, we are increasing the timeout manually using the context.
Happy to contribute if it needs it and also hear other thoughts about it. 😊
The text was updated successfully, but these errors were encountered: