Frequent Asked Questions
Isn't XML slow ?
See full demo website : XML, DOM, XSL are fast enough.
Should I use XsltCMS for a big website ?
No if :
- You have A LOT of data (i.e. more than 10Mo of text, that is probably less than 1% of websites)
- You need some advanced workflow process (someone write, someone else validate, etc.)
How to cluster / replicate ?
XsltCMS is very easy to distribute over a lot of server, as all public file produced are static : copy them (for instance each night) to every server. That's all. (private access should be in that case made to only one server, perhaps dedicated to that).
Isn't static file creation very insecure, as a read and write directory is needed ?
Avoiding giving writing rights to your webserver user (whichever operating system you use) is only one of your defense againt hacking, and generally one the the weaker ones. In order to abuse it, one must be able to open a session in your own webserver, then find blindly this directory. This happening is a major failure, that will be abused massively by other means anyway.
If this is still a problem, you can see the solution applied to the complex website demo (generating .htacces by templates)