12 Aug
2009
12 Aug
'09
9:03 a.m.
Trevor wrote:
Hi Guillaume,
Thanks for your detailed reply, I appreciate it.
On Tue, 11 Aug 2009 18:59:15 +0200 Guillaume Lerouge <guillaume(a)xwiki.com> wrote:
Jetty is good enough as a container for production use. Even Google
recently switched from Tomcat to Jetty for its hosted apps. HSQLDB, on
the other hand, is not suited for big wikis, since it keeps all the data
in memory.
Brand new WYSIWYG editor.
We've got a great new skin / user interface on the way that's even better
than the current one.
Are you referring to v2.0 compared to v1.9?
One of our primary criteria is a well-rounded, solid WYSIWYG editor (for non-technical
users), and I'm currently basing my judgement on v2.0 milestone 2. Is v2.0 running
"well enough" to use on a lightly-used production server? Any timeline on when
it will be released officially?
effects). A way to prevent this is to use XWiki
Enterprise Manager, to open
one wiki per client (clients having local accounts on those wikis) while
your developers will be global users with access to all subwikis. That would
fit neatly with your use case I believe.
Yes, I think that sounds like it would do what we need. Is XEM released for v2.0 yet?
Or would we have to run 1.9?
Another question, regarding the choice of database: the download page says "Once
you're more familiar with XWiki you might want to set it up on your own database or in
your own container,..." Does this mean Jetty and/or HSQL are not robust enough for a
production wiki instance? When it says "Standalone installation including a Jetty
container and an HSQLDB database all set up." it seems to imply that this is *just*
for first-time, inexperienced users, and maybe not for a live production system. Ah, I see "Currently XEM only fully supports
MySQL and Oracle RDBMS."
Thanks again for your candid answers.
If any users on the mailing list have trials or tribulations with these servlets and/or
databases, any comments would be welcome.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/