On 27 Jan 2012, at 20:27, John Fereira wrote: > Sure, I could dump the RDF, but the site is going to be harvesting data from > numerous data sources, probably on a daily basis and considering it's going > to be hosted at a well known U.N. organization it's likely going to get > really large. If I was just going to use RDF I could that directly to Elda > and forget about using joseki/fuseki entirely (which I might do for a subset > of the data anyway). > > The semantic web app isn't so much tightly coupled with SDB as much as SDB > is sort of hardwired into it. I suppose replacing it with TDB would be > possible but that would make it quite difficult to migrate to future release > of the app.
I've had a quick look at getting connection pooling working with fuseki and it looks tricky. The problem is that there's no obvious point to free the connection. Two approaches: 1) Wrap every DatasetGraph operation in a getConnection / freeConnection and use a pool. That might be ok for fuseki. Generally it won't work because you can get a graph and perform arbitrary operations on it. 2) Before every SDB operation check the status of the connection (e.g. 'SELECT 1') and, if necessary, reconnect. Will investigate later. Damian
signature.asc
Description: Message signed with OpenPGP using GPGMail
