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

Chain content instead of replacing it #173

Closed
Kaliumhexacyanoferrat opened this issue Jan 15, 2021 · 0 comments · Fixed by #189
Closed

Chain content instead of replacing it #173

Kaliumhexacyanoferrat opened this issue Jan 15, 2021 · 0 comments · Fixed by #189
Labels
enhancement New feature or request
Milestone

Comments

@Kaliumhexacyanoferrat
Copy link
Owner

As a developer of a web application, I would like the checksum calculation to be as effective as possible, so the caching functionality requires less computation resources. Therefore, concerns should not override the content with an expensive checksum calculation method based on a stream, but re-use the existing content to have a very fast checksum calculation.

Example

response.Content = new GzipContent(response.Content);

Acceptance criteria

  • All concerns are rewritten to efficiently pass the checksum calculation through to the actual source
@Kaliumhexacyanoferrat Kaliumhexacyanoferrat added the enhancement New feature or request label Jan 15, 2021
@Kaliumhexacyanoferrat Kaliumhexacyanoferrat linked a pull request Jan 15, 2021 that will close this issue
@Kaliumhexacyanoferrat Kaliumhexacyanoferrat added this to the Version 5.2 milestone Jan 15, 2021
@Kaliumhexacyanoferrat Kaliumhexacyanoferrat removed this from the Version 5.2 milestone Jan 16, 2021
@Kaliumhexacyanoferrat Kaliumhexacyanoferrat added this to the Version 5.3 milestone Feb 21, 2021
@Kaliumhexacyanoferrat Kaliumhexacyanoferrat linked a pull request Mar 2, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant