From: Lars H. <he...@se...> - 2008-04-23 17:34:41
|
Hi, Here a short overview what has changed from 1.0 to the current SVN version: - Automerge is not supported anymore Reason: tinyTiM does not ensure that the topic references are kept valid. We'd have to use a mechanism like TM4J where the merged topics reference to each other. This is more work than necessary, I think. - Merging works (at least it should ;)) Merging does suppress duplicates and ensures that all topic characteristics are transferred from one topic to the other. (Topic map merging does not work yet, but should tomorrow) The new merging mechanism bypasses TMAPI and works on top of tinyTiM's own API which should result in a faster merging process - Two non-TMAPI indexes: TypeInstanceIndex and ScopedIndex. These are used while merging and they have a simplified API compared to the quite heavy TMAPI index API - Introduced interfaces IReifiable, ITyped etc. These interfaces simplify access to TMDM features. I think we should remove these if we move to TMAPI 2.0 - Configurable collection factory It's possible to replace the collection factory (factory used to create all Maps / Sets in the core) with a custom implementation. Currently, tinyTiM supports a TroveCollectionFactory (if Trove4J is found in the class path) and a standard JavaCollectionFactory which uses the standard Java Collections. - Some kind of event API Well, this is not meant to be utilised by 3rd parties and needs more work, I guess. - Java 1.5 (where possible since TMAPI is not 1.5-aware) Best regards, Lars -- http://www.semagia.com |