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.

Sign up for GitHub

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

Jump to bottom

Investigate if a transport parameter is needed for REST LRO client classes #726

Open
ohmayr opened this issue Oct 8, 2024 · 0 comments
Open

Investigate if a transport parameter is needed for REST LRO client classes #726

ohmayr opened this issue Oct 8, 2024 · 0 comments
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: cleanup An internal cleanup or hygiene concern.

Comments

@ohmayr
Copy link
Contributor

ohmayr commented Oct 8, 2024

We currently have separate client classes for each combination of [async, sync] x [gRPC, REST] transports. We also maintain separate transport classes for REST.

Given the above case, it's worth figuring out if a transport parameter adds any value in the REST client classes.
@ohmayr ohmayr mentioned this issue Oct 8, 2024
Merged
@vchudnov-g vchudnov-g removed their assignment Oct 17, 2024
@vchudnov-g vchudnov-g added type: cleanup An internal cleanup or hygiene concern. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. type: cleanup An internal cleanup or hygiene concern.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vchudnov-g @ohmayr