Skip to content

Strategy for dual-mode APIs (REST + gRPC) #1696

@tseaver

Description

@tseaver

For the APIs which support both REST and gRPC, how should we expose the choice? One option would be to have a different Connection class for each endpoint: if it works, then after instantiating the desired client, calling code would in theory be happy without caring again which one was chosen. Thoughts?

Because the datastore API is protobufs-over-REST, its Connection class already has a bunch of domain-specific API calls already, which would make this plan simpler. the Connection classes for pubsub and logging expose only make_api_request, which won't be much help.

Metadata

Metadata

Assignees

Labels

api: datastoreIssues related to the Datastore API.api: loggingIssues related to the Cloud Logging API.api: pubsubIssues related to the Pub/Sub API.type: questionRequest for information or clarification. Not an issue.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions