A TDB dataset only allows a single JVM to access/manage it at a time. It is my understanding that Fuseki is primarily simply a SPARQL endpoint server to issue queries to for one or more TDB datasets. One can also write their own TDB application, creating their own TDB access server, using the TDB libraries. While it is possible to support SPARQL queries through the TDB libraries, it “may” be the case that the multi-client serviceability mechanisms that are built into Fuseki are not directly available in the TDB libraries if one is wanting to also add their own non-SPARQL access code. I believe it is the case that TDB would not allow both a Fuseki server as well as one’s own server accessing the same TDB instance. Is there any means to enable a hybrid approach, where you can have a server that includes all the capabilities provided by Fuseki, but also allow for extending that server to support access to code that one would write directly against the TDB and Jena libraries?
David Jordan Senior Software Developer SAS Institute Inc. Health & Life Sciences, Research & Development Bldg R ▪ Office 4467 600 Research Drive ▪ Cary, NC 27513 Tel: 919 531 1233 ▪ [email protected]<mailto:[email protected]> www.sas.com<http://www.sas.com/> SAS® … THE POWER TO KNOW®
