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.

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

GridFS backend: store response metadata in regular MongoDB collection, and response body in GridFS #581

Open
JWCook opened this issue Apr 13, 2022 · 1 comment
Labels
backends Features or changes related to specific backends enhancement

Comments

@JWCook
Copy link
Member

JWCook commented Apr 13, 2022

Related to #576.

This would require adding a 3rd storage object for response content. So a total of 1 GridFS store, and 2 MongoDB collections:

  • content
  • responses
  • redirects

Handling that will require overriding several BaseCache methods.

@JWCook JWCook added enhancement backends Features or changes related to specific backends labels Apr 13, 2022
@JWCook JWCook added this to the Long-term backlog milestone Apr 13, 2022
@JWCook
Copy link
Member Author

JWCook commented Apr 13, 2022

This is an idea for the future, but not planning to implement it right now.

@JWCook JWCook closed this as completed Apr 13, 2022
@JWCook JWCook changed the title GridFS backend: store response metadata in regular MongoDB collection, and response content in GridFS GridFS backend: store response metadata in regular MongoDB collection, and response body in GridFS Apr 20, 2022
@JWCook JWCook reopened this Apr 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backends Features or changes related to specific backends enhancement
Projects
None yet
Development

No branches or pull requests

1 participant