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

Consider using POST instead of GET for resource reads #535

Open
jberdine opened this issue Nov 25, 2024 · 0 comments
Open

Consider using POST instead of GET for resource reads #535

jberdine opened this issue Nov 25, 2024 · 0 comments
Labels
api-change Public API (breaking) change

Comments

@jberdine
Copy link
Contributor 

          To expand on my previous reply, we could replace `GET /v1/resource/:resource` with a `POST /v1/snapshot` passing the `resource` and `params` (and possibly a set of `keys`) as a JSON object in the request body. This would also stress the fact that doing a sync read does indeed involve instantiating a resource.

Originally posted by @beauby in #514 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
api-change Public API (breaking) change
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jberdine