Uploaded image for project: 'HttpComponents HttpClient'
  1. HttpComponents HttpClient
  2. HTTPCLIENT-2068

Caching HttpClient: Add ability to invalidate cached responses upon revalidation

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Wish
    • Status: Closed
    • Major
    • Resolution: Not A Problem
    • 4.5.12
    • None
    • HttpCache
    • None

    Description

      Hi there,
      I've been playing around with the Caching HttpClient a bit. It works nicely, but one thing really is of concern for me:

      When dealing with lots of identical requests, the cacheDir quickly gets filled up with copies of all the same files.

      I understand that technically these responses have not been invalidated due to the new request, but from my perspective it would make sense to invalidate them because they are technically superseded by the new response. Or even better, use the same file for all responses, as that would save IO on high-throughput systems.

      Thanks in advance for your time and keep up the good work!

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            philippn Philipp Nanz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment