On 28 May 2013 03:50, Sebastian Schaffert <sebastian.schaff...@gmail.com>wrote:
> Hi Raffaele, > > first of all: I did a number of database improvements. Maybe you can check > how in your example this affects performance (check out the latest source > release in the development branch)? > > Most of the refactoring for this change has already been done, the main > things that are needed are: > - allow SesameService to inject different implementations of storage > backends, in the same style it already handles SailProviders > - create separate modules for the different backends (e.g. > marmotta-backend-kiwi, marmotta-backend-native, marmotta-backend-bigdata, > marmotta-backend-tdb, marmotta-backend-sdb) > - check which other modules are affected by this change, e.g. the current > versioning and reasoning will only work with the kiwi backend, but other > backends also support different kinds of reasoning so maybe the > marmotta-reasoner can be made more generic to support different styles of > reasoning, or there are different reasoning modules depending on the > backend like marmotta-reasoner-kiwi, marmotta-reasoner-bigdata, ... > > What I still need to think about is how to ensure only one backend is used > even if several are found on the classpath - because unfortunately Maven > does not provide a way to define mutual exclusion of dependencies (or does > it?). Maybe the user would even want to be able to select the backend at > runtime - but then this has consequences on which other modules are > available. > > > Since I probably know the architecture best, I will try to provide the > necessary infrastructure in the coming weeks. In the meantime, if you want > to work on a Sesame API wrapper for Jena SDB and TDB, this would be a major > step towards this goal. ;-) > > If you can do this generically, as a Sail then it would have a large audience, based on current interest in the JenaSesame wrapper. Cheers, Peter
