Uploaded image for project: 'JBoss Cache'
  1. JBoss Cache
  2. JBCACHE-118

Inefficient CacheLoader.exists() followed by CacheLoader.get()

    Details

    • Type: Task
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: 1.2.1
    • Fix Version/s: 1.3.0.GA
    • Component/s: None
    • Labels:
      None

      Description

      I have a CacheLoader that I am using to allow a TreeCache to act as the primary interface to a DAV/JDBC data model. Each access to the backend can be quite expensive. I note that a CacheLoader.get() is always preceeded by a CacheLoader.exists(), which seems redundant to me and has the unfortunate effect of doubling the backend load. Am I missing something here?

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  manik Manik Surtani
                  Reporter:
                  belaban Bela Ban
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: