Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-6891

Investigate concurrency improvements to DerbyObservable and DerbyObserver

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • Store
    • None
    • Normal

    Description

      As part of derby-6856, we introduced a pair of classes which manage callbacks between classes in the Store layer. The classes are DerbyObservable and DerbyObserver. They replace the deprecated Observer and Observable classes in the JVM and allow Derby to build without deprecation warnings. Right now, callbacks are managed by a Vector. It is quite likely that the concurrency of these classes (and therefore of the Store layer) could be boosted by using some mechanism from java.util.concurrent.

      Attachments

        1. derby-6891-01-aa-synchronizeMethods.diff
          2 kB
          Richard N. Hillegas
        2. derby-6891-01-ab-synchronizeMethods.diff
          3 kB
          Richard N. Hillegas

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. DERBY-6856 Make it possible to build Derby using JDK 9

          • Major - Major loss of function.
          • Closed

          Activity

            People

              Unassigned Unassigned
              rhillegas Richard N. Hillegas
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: