You can try disabling the cache and changing this property:
<contentstore classname="
org.apache.slide.store.txfile.TxFileContentStore">
<parameter
name="rootpath">store/content</parameter>
<parameter
name="workpath">work/content</parameter>
# <parameter
name="defer-saving">true</parameter>
<parameter
name="defer-saving">false</parameter>
<parameter
name="timeout">120</parameter>
</contentstore>
without cache and with defer-saving off, you will still have
to somehow
indicate to the read only content store that the modifiable
content store
has received changes. Again, I recommend using a software
package that
solves the specific problem you are trying to solve and is
integrated into
slide. Slide has an API for this purpose.
If you choose to use a database, which I actually recommend,
you will still
have to concern yourself with concurrency if you choose to
run two slide
servers.
On 1/30/07, Jean-Francois Gosselin <jfgosselin yahoo.com> wrote:
>
> To summarize, I want to share the content store between
two WebDav servers
> but I want to use the file system (NAS, SAN).
> The content is modified (PUT, COPY , DELETE, etc) only
through one of the
> server and the other one is used in read-only (GET) .
You can try disabling the cache and changing this property:
<contentstore classname="
org.apache.slide.store.txfile.TxFileContentStore">
<parameter
name="rootpath">store/content</parameter>
<parameter
name="workpath">work/content</parameter>
# <parameter
name="defer-saving">true</parameter>
<parameter
name="defer-saving">false</parameter>
<parameter
name="timeout">120</parameter>
</contentstore>
without cache and with defer-saving off, you will still have
to somehow
indicate to the read only content store that the modifiable
content store
has received changes. Again, I recommend using a software
package that
solves the specific problem you are trying to solve and is
integrated into
slide. Slide has an API for this purpose.
If you are really looking to just share the contents of an
existing file
system via webdav, you should look into use SimpleFileStore.
A transactional
information retrieval system, such as TxFileContentStore is
not a utility
for sharing a file system. This infrastructure performs
version control,
branching, and mutiuser management.
Is it possible without a database ?
If you choose to use a database, which I actually recommend,
you will still
have to concern yourself with concurrency if you choose to
run two slide
servers.
-mike
|