Hello Mike, thank you for the response.
At our company we're using both the ruby and the java client libraries for Google Ads API. In the Java client lib the page size can be specified. I wonder whether client libraries could handle the optimal page size themselves, since exposing a row-based page size (when the underlying gRPC uses bytes for page limits) doesn't really make sense with arbitrary sized rows depending on the account, GAQL query or date range. The streaming option sounds like a reasonable solution for this problem. Do you have any rough date available when this improvement on the page handling will be available? Thanks, Robert -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/adwords-api. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/fdeb90d9-f49e-4b9e-8586-93f1c6124738%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
