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

Investigate concurrency improvements to DerbyObservable and DerbyObserver

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Store
    • Labels:
      None
    • Urgency:
      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

        Issue Links

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              rhillegas Richard N. Hillegas

              Dates

              • Created:
                Updated:

                Issue deployment