31 Jan
2011
31 Jan
'11
9:59 p.m.
Le 31 janv. 2011 à 19:48, Sergiu Dumitriu a écrit :
Actually, the goal is the converse: the internal, robot-oriented xwiki would read the
cloned DB.
The interest
is that it could allow some of the web requests to be served by a database that is a slave
of the main database, in live synchronization with the master MySQL.
You mean that the public wiki reads data from the read-only database,
which is actually updated by cloning another read-write database updated
from a private wiki? That's an interesting idea for securing a public
server.
could be though you need a filtering mechanism thn.
You should also set in xwiki.cfg:
xwiki.readonly=1
why *also* ?
This might reduce some of the errors that you get,
although there's a
lot of code that ignores this setting. It would be nice if you could
report (on jira) what exactly breaks so that we can fix it properly.
If you say a lot of code ignores that than I'd better not rely on it I'm afraid.
Nonetheless, the previous option sounds good.
paul