Hi, The SingleTdbDatasetTcProvider probably performs a little better for a small number of graphs. Otherwise I see no real benefit.
ScalableSingleTdbDatasetTcProvider is/was my first contribution intended to replace the original SingleTdbDatasetTcProvider. However replacing from the start might have been a to big change, so I created sort of a duplicate. If others are satisfied with the scalable version as well then we could drop the old on. Please not that I still occasionally get a concurrent modification exception, but I think the original has the same flaw. Also note that the Sesame based Provider (rdf.sesame.storage) has the exact same scalability issues. When I have time I will redo the same changes for that implementation. Regards, Minto Op 15-7-2013 15:47, Reto Bachmann-Gmür schreef: > Hello > > As some refactoring is needed to correctly support the default graph > I'm wondering what's the justification for having 2 > SingleTdbDatasetTcProvider. I understand > ScalableSingleTdbDatasetTcProvider works better for large number of > graphs, but what are the advantages of the original one? > > Cheers, > Reto -- ir. ing. Minto van der Sluis Software innovator / renovator Xup BV Mobiel: +31 (0) 626 014541
