Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ferature Request: Add support for Batch Requests #5

Open
chrisabruce opened this issue Dec 1, 2020 · 2 comments
Open

Ferature Request: Add support for Batch Requests #5

chrisabruce opened this issue Dec 1, 2020 · 2 comments

Comments

@chrisabruce
Copy link

As documented here: https://developers.google.com/gmail/api/guides/batch it would be ideal to also add support for batch requests.

@dermesser
Copy link
Owner

This is something I overlooked in the first iteration to gain simplicity (we now have three or four request methods used for all calls). This probably needs a way to represent requests as objects that can be sent one-at-a-time or multiple at once by a call.

@dermesser
Copy link
Owner

I was wondering here - with async operations, is there a big difference between sending batch requests in the first place and sending several requests at once, and join!ing/join_alling them? And given that the batch interface is usually "concatenate raw HTTP requests into a multipart/mixed body", which brings considerable complexity into the picture, this may actually be not that bad as an alternative (caveat: as long as hyper does this the way I hope it does, i.e. using HTTP/2 as it is intended to be used, with concurrent streams etc.)

It shouldn't make a big difference in terms of quota, or transferred data volume, while keeping the logic much more simple. What am I missing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants