Uploaded image for project: '[Read Only] - Hippo Site Toolkit 2'
  1. [Read Only] - Hippo Site Toolkit 2
  2. HSTTWO-1976

Abstract the pooled jcr session refresh into a pluggable mechnism, to be able hook in different refreshing calls later, for example one that only disposes virtual session states

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • High
    • Resolution: Fixed
    • None
    • 2.22.10, 2.24.02, 2.25.00-alpha
    • None
    • None

    Description

      Ard recommeded this:

      > If we want to gain some real 'short-term' improvements without having
      > to wait for fundamental model changes, what do you think if we try to
      > get the HippoSession method disposeVirtualStates() into the Hippo
      > repository. Then, I think we can do with quite some less Session
      > refreshes
      >
      > HippoSession extends Session

      { > void disposeVirtualStates() throws RepositoryException; > }

      >
      > This way, all our 'read-only' jcr sessions in the default session pool
      > never need a refresh, but just a disposeVirtualStates() call when
      > there was an event below /content caught
      >

      I think the BasicPoolingRepository#SessionFactory#activateObject() could
      do it optionally (this can be the default configuration through
      SpringComponentManager.properties by the way). The proxy session could
      implement #disposeVirtualStates() to enable this.

      Attachments

        Issue Links

          Activity

            People

              aschrijvers Ard Schrijvers
              wko Woonsan Ko (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: