Hi Matt, > It took a while, but we have finally released AxKit2, version 1.0.
I'm very excited to see that AxKit2 finally takes off - but also a bit confused as I seem to miss a lot of features from 1.X. My company is preparing a huge development project based on AxKit - a virtual document management system. The core will be built on top of AxKit, and we plan to contribute the whole core to the community. Security, however, will be a very important factor, and we planned to use almost all of Apache's security measures - including stuff like digital certificates to identify the user etc. We can still do that by proxying through Apache, of course. But what about virtual hosting? I run a webhotel based on AxKit with a lot of virtual servers: With your new architecture, wouldn't that mean running a lot of AxKit servers on different ports, one for each virtual server? And then proxying through Apache in order to get them all back at port 80 - or am I missing something here? I wouldn't describe this as a simpler setup... On the other hand I like the idea (and simplicity) of beeing able to run AxKit standalone: But like Tomcat, maybe we should have both options? By the way, we're running SuSE Linux and at least with that distro, installing Apache and mod_perl is simply a few clicks with the mouse and you're up and running; it's a long time since I thought installing mod_perl was any hassle at all ;-). The new AxKit2 architecture seems to be a lot more complicated to me - at least when you need some of the more fancy Apache options. Regards, Lars -- Lars Skjærlund Skovengen 111 2980 Kokkedal Denmark Tel.: +45 70 25 88 10 http://www.skjaerlund.dk/lars --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
