Changes between Version 56 and Version 57 of ReleaseNotes

Timestamp:

30.01.2013 19:09:29 (12 years ago)

Author:

jri

Comment:

4.0.14 release notes, pt. 3

ReleaseNotes

@@ -5 +5 @@
 ----
 
-== 2013-1-?: DeepaMehta 4.0.14 ==
+== 2013-01-30: DeepaMehta 4.0.14 ==
 
 Main focus of !DeepaMehta 4.0.14 is better **Performance** for large data amounts. Read about the [[https://lists.berlios.de/pipermail/deepamehta-users/2013-January/000404.html|problem background]] in this posting.
@@ -12 +12 @@
 
 Main aspects of the new storage layer:
-* **High-speed traversal:** Traversal is significantly speed up by utilizing a Lucene index for association metadata. In particular, highly connected nodes ("supernodes") have no negative impact on traversal speed anymore (#389).
-* **Compact architecture:** The concept of a DM-independant !MehtaGraph API is abolished. A storage implementation is coded directly to the !DeepaMehta model API. The additional bridging layer is dropped. There is no dependency on the external Neo4j !MehtaGraph library anymore (#389). 
-* **Modular storage layer:** a new service provider interface (`de.deepamehta.core.storage.spi.DeepaMehtaStorage`) allows 3rd-party developers to implement an alternate !DeepaMehta storage layer, based on another DB than Neo4j. Storage layer implementations are deployed as OSGi services (#391).
-* Association user data is indexed as well (like topic user data) (#389).
+* **High-speed traversal:** Traversal is significantly speed up by the means of a Lucene index for association metadata. In particular, highly connected nodes (so called "supernodes") have no negative impact on traversal speed (#389).
+* **Compact architecture:** The concept of a DM-independant !MehtaGraph API is abolished. A storage implementation is coded directly to the !DeepaMehta Model API. The additional bridging layer is dropped. There is no dependency on the external Neo4j !MehtaGraph library anymore (#389). 
+* **Modular storage layer:** a service provider interface (`de.deepamehta.core.storage.spi.DeepaMehtaStorage`) allows 3rd-party developers to implement alternate storage layers for !DeepaMehta, based on DBs other than Neo4j. A Storage layer implementation is deployed as an OSGi service (#391).
+* **1st-class associations**: Association user data is indexed as well (just like topic user data) (#389).
 
 Additional performance measures:
-* For DB read operations no transactions are created anymore (#406).
-* Delivering core events involves no runtime reflection anymore (#352).
+* For DB read operations no transactions are created (#406).
+* Delivering core events involves no runtime reflection (#352).
 
 Further improvements: