On 28-Aug-06, at 3:36 AM, Lars Skjærlund wrote:
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.
They're coming :-)
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.
That's awesome news.
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.
Indeed. To make this easier I'll be adding something to the docs to
show how to setup in an Apache environment. In the meantime here's
how I have my gallery working on apache2:
NameVirtualHost 62.173.71.110
<VirtualHost 62.173.71.110>
ServerName home.sergeant.org
ProxyRequests Off
ProxyPass / http://home.sergeant.org:8001/
ProxyPreserveHost On
</VirtualHost>
My other vhosts proxy through to host:8000 which is AxKit1, but I'll
be migrating more to AxKit2 as I find time.
Note that running extra ports with axkit2 is trivial and doesn't
require extra servers to run (no more memory used):
<Server abc>
Port 8001
...
</Server>
<Server xyz>
Port 8002
...
</Server>
etc.
But for the cases where you need AxKit2 to be the front-end server
I'll be looking at adding vhost support at some point. It shouldn't
be too hard.
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?
Not sure I understand this point - Tomcat is always standalone. If
you run it via Apache it's just a proxy (albeit not using http).
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.
I want to be able to run without Apache. Maybe on an IIS setup, or
lighttpd, or in places where I don't want to install a web server.
This is pretty much the only way you'd get that flexibility.
Plus this way debugging and profiling is infinitely easier than under
mod_perl. And for those who've hacked on AxKit2 so far they all say
development is easier.
Matt.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
