Uploaded image for project: 'SignServer'
  1. SignServer
  2. DSS-2233

Make QoSFilter optional

    Details

    • Type: Task
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: QoS Filter
    • Labels:
      None

      Description

      Currently in trunk the QoSFilter is always active.
      Since it intercepts requests and could affect performance we should make it optional.

      • One idea: have a global property and either:
        • Decide at init() to enable filtering or not
        • At each request update state (possibly using config cache to avoid repeated EJB lookups).

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              marcus.lundblad@primekey.se Marcus Lundblad
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1 day
                  1d
                  Remaining:
                  Remaining Estimate - 1 day
                  1d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified