[EMAIL PROTECTED] at [EMAIL PROTECTED] wrote:
>
> Well, most of the complexity comes from the fact that it abstracts the
> interface with the server - it was designed from the beginning with the
> idea that it should support multiple servers.
>
> Right now the list is: Apache1.3, Apache2.0, IIS, NES, AOLServer.
>
> It was also designed from the beginning with the idea that it should
> support multiple communication protocols - that means new depvelopment
> will have minimum impact on the stability.
>
> It also means you can fine-tune your configuration to the caracteristics
> of the apps ( apps that are doing a lot of IO but little computation could
> use JNI, apps that are compuation intensive could be distributed on remote
> servers and load-balanced, etc ).
>
> Yes, the code is quite sophisticated - but I'm not sure you'll find too
> many apache modules that also work with IIS,NES,etc and have this
> flexibility.
You're saying this as if the WebApp module was not thought with the same
idea but was a piece of crap...
One day, without compromising its internals, the WebApp module will support
those features, and many more... But I'm just one, and my days are (yes for
me too) 24 hours long...
Pier
