René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"API differences between HTTP and gRPC implementations","articleBody":"We have two methods of interacting with the API backend: gRPC (default) and HTTP (used when client is created with `google.cloud.logging.Client(_use_grpc=0)` or `DISABLE_GRPC` is set).\r\n\r\nThis is implemented using two _*API implementations: One in [_http.py](https://github.com/googleapis/python-logging/blob/ff90fd2fb54c612fe6ab29708a2d5d984f60dea7/google/cloud/logging_v2/_http.py) and the other in [_gapic.py](https://github.com/googleapis/python-logging/blob/master/google/cloud/logging_v2/_gapic.py). It looks like in some cases, they return different values (_http returns a page iterator object directly, while _gapic often converts it to a generator. This confuses users who expect high-level APIs to act consistently regardless of the implementation used.\r\n\r\nI suggest we refactor _http.py to be consistent with _gapic.py, and add tests to make sure they act consistently","author":{"url":"https://github.com/daniel-sanche","@type":"Person","name":"daniel-sanche"},"datePublished":"2021-01-13T19:38:07.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/154/python-logging/issues/154"}