You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by oz...@apache.org on 2005/01/08 20:48:31 UTC
cvs commit: jakarta-commons/transaction RELEASE-NOTES.txt
ozeigermann 2005/01/08 11:48:31
Modified: transaction RELEASE-NOTES.txt
Log:
Adjusted release notes to current status
Revision Changes Path
1.10 +16 -7 jakarta-commons/transaction/RELEASE-NOTES.txt
Index: RELEASE-NOTES.txt
===================================================================
RCS file: /home/cvs/jakarta-commons/transaction/RELEASE-NOTES.txt,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- RELEASE-NOTES.txt 7 Jan 2005 13:32:33 -0000 1.9
+++ RELEASE-NOTES.txt 8 Jan 2005 19:48:31 -0000 1.10
@@ -21,15 +21,23 @@
This is the first beta of the Commons Transaction 1.1 feature release.
-Commons Transaction 1.1 aims at polishing (interface) oddities, improve
-locking and make the file store more flexible.
+Commons Transaction 1.1 aims at polishing (interface) oddities, improving
+locking and making the file store more flexible. Locking now is much more
+flexible, extensible and allows for rudimentary transaction management. There
+is a new lock manager hides locks from the user and keeps track of all of them
+allowing for deadlock detection and more convenient management.
ENHANCEMENTS FROM 1.0
---------------------
Locking:
-- Extended and less excentric lock manager
-
+- Extended and less excentric lock manager interface LockManager2
+- Extended multi level lock interface MultiLevelLock2
+- GenericLock and GenericLockManager now implement new interfaces as well
+- GenericLock and GenericLockManager offer much better inspection with toString
+- GenericLock offers (protected) means for waiter management and opens
+ possibility for fair strategies to subclasses
+
File:
- Confiburable resource id to path mapping
@@ -38,9 +46,10 @@
Locking:
- new ReadWriteLockManager for most intuitive read/write lock usage
-- new read/write/upgrade locking mechanism
+- new read/write/upgrade locking mechanism (ReadWriteUpgradeLock, ReadWriteUpgradeLockManager)
- Deadlock detection for all lock managers, file store, and pessimistic map
-- Flexible preference locking mechanism
+- Flexible preference locking mechanism
+- Global transaction timeouts that actively revoke granted rights from transactions
MINOR INCOMPATIBILITIES TO 1.0
-----------------------------------------
@@ -54,4 +63,4 @@
KNOWN ISSUES
------------
-none
+- Deadlock detection rarely determines more than one thread as a deadlock victim
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org