Hi Thomas, Thanks for the reply, it definitely clears a few things up for me. I like your suggestion of a new Data Store. On a scale of 1-10, how difficult do you think it would be?
I was thinking it would be a matter of launching a thread for each write operation performed. There would have to be a database configured on the second drive, but after the write completes the threads just join. This would keep everything in sync as far as I can tell (with the exception of a hardware error). This doesn't seem like a huge modification outside of adding some configuration options and probably duplication of the schema to the second drive on init. Your thoughts? Thomas Mueller-6 wrote: > > Hi, > >> Right now I'm assuming binary data is written directly to the >> file system even when using "SimpleDbPersistenceManager". > > You can configure this. See > http://jackrabbit.apache.org/api-1/org/apache/jackrabbit/core/state/db/SimpleDbPersistenceManager.html > > SimpleDbPersistenceManager > It is configured through the following properties: > * driver: the FQN name of the JDBC driver class > * url: the database url of the form jdbc:subprotocol:subname > * user: the database user > * password: the user's password > * schema: type of schema to be used (e.g. mysql, mssql, etc.); > * schemaObjectPrefix: prefix to be prepended to schema objects > * externalBLOBs: if true (the default) BINARY values (BLOBs) are > stored in the local file system; if false BLOBs are stored in the > database > > The last option is what you are looking for. > > Another idea would be to use the new DataStore, but first somebody > would need to build a 'replicating data store'. > > Thomas > > -- View this message in context: http://www.nabble.com/Local-content-replication-tf4465166.html#a12743177 Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
