db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6891) Investigate concurrency improvements to DerbyObservable and DerbyObserver
Date Sat, 25 Jun 2016 17:09:37 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15349727#comment-15349727

ASF subversion and git services commented on DERBY-6891:

Commit 1750214 from [~rhillegas] in branch 'code/trunk'
[ https://svn.apache.org/r1750214 ]

DERBY-6891: Improve the synchronization behavior of DerbyObservable; commit derby-6891-01-ab-synchronizeMethods.diff.

> Investigate concurrency improvements to DerbyObservable and DerbyObserver
> -------------------------------------------------------------------------
>                 Key: DERBY-6891
>                 URL: https://issues.apache.org/jira/browse/DERBY-6891
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>            Reporter: Rick Hillegas
>         Attachments: derby-6891-01-aa-synchronizeMethods.diff, derby-6891-01-ab-synchronizeMethods.diff
> 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.

This message was sent by Atlassian JIRA

View raw message