Uploaded image for project: 'mod-authtoken'
  1. mod-authtoken
  2. MODAT-49

Two caches for permissionsForUser and expandPermissions

    XMLWordPrintable

    Details

    • Template:
    • Sprint:
      CP: sprint 73
    • Story Points:
      3
    • Development Team:
      Core: Platform

      Description

      Adam wrote on https://github.com/folio-org/mod-authtoken/pull/53 :

      Note that the caching is still sub optimal.. There should be two cache entries.. Not one.

      The first (and existing one) should cache the result of getPermissionsForUser. So the key obviously depends on user and tenant.

      The second is the call toexpandPermissions. It does NOT depend on the user. This is important. The cache entry for that one can have a long TTL, because it only depends on ModuleDescriptors enabled for the tenant. These rarely changes!!!

      I think the code would also be clearer if it was a simple "intercept" of those calls. Since the former have a short TTL it makes the 2nd call being called at times where that is not necessary.

      If the cache are separate it also means the CacheEntry is simpler.

        TestRail: Results

          Attachments

            Issue Links

            relates to

            Bug - A problem which impairs or prevents the functions of the product. CHAL-79 Check in takes ~4 sec when item has request on it

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Sub-task - The sub-task of the issue CIRC-452 analyze inventory/items?query=barcode=xxx

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. MODAT-47 Incorrect extra permissions handling

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Task - A task that needs to be done. MODAT-51 investigate potential mod-authtoken performance issue

            • P2 - normal priority level, must be included in the current development cycle
            • Blocked

            Bug - A problem which impairs or prevents the functions of the product. UICHKIN-111 Check in takes ~4 sec when item has request on it

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

              Activity

                People

                Assignee:
                adam Adam Dickmeiss
                Reporter:
                julianladisch Julian Ladisch
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases