3
the first item on the docs agenda is user documentation. Developer documentatin is also being made as the developers go, but that is mostly focussed on creating modules and code use, not architecture and concepts. XOOPS is a PHP application that runs with a minimum of apache modules installed (basic default setup of apache works), but also works on IIS, so there isn't anything to report on apache integration that isn't covered by decent (3rd party) webserver setup documentation.
As for the cache manager, I believe it is tied in with the Smarty engine (but I could be wrong! I am not a developer who was involved in the 2.0 core development). More info about Smarty can be found at
http://smarty.php.net.
About SSH, I haven't seen it working anywhere yet, not have I had any reports of it working anywhere, allthough the general prefs page does list the option to use https. So, I can't say much on that, sorry.
About performance: there are a couple of long posts about this in the forum, but mostly with complaints (logically). Most sites that use XOOPS with large amounts of traffic run smoothly, as long as their hardware is up to specs. We don't have the resources to do these extensive tests, buy SSH certificates, or write quality documentation quickly on the fly. This isn't an ideal situation, I agree, but we have to get by with what we do have.
Most of these issues are being addressed, but may be relatively low on the priorities list.
Herko
