[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> From my end user (production) point of vue, I need the fastest servlet-engine
> with a robust WEB Server (Apache) connector. Like many I select ApacheJServ
> and next TC 3.x because there was mod_jserv (load-balancing and
> fault-tolerance).
If you see the source code in the "connectors" directory, you'll notice how
easy it is to add load balancing and fault tolerance to the new modules.
There are two main concepts for achieving this: providers and connections. A
provider is a plug in to the webapp library that actually deals with
communication between the web server and the servlet engine, and connections
are the actual configured connections (each associated with one provider)
between the w/s and the s/e.
You can write easily a load-balancing provider wich will balance requests on
a bunch of other configured connections....
> I'll really start to test TC 4.x when such a connector will be available. I'll
> check speed, stability and memory use. Did we must espect TC 4.x to be much
> more hungry of bytes that 3.x ?
Slightly bigger in memory... The actual module (-O6) is 16 Kb (including the
library) but at run time you should expect to see variances up to 50 kb per
request... The consumed memory is bigger because the actual connection
doesn't rely on the web server API anymore..
> I'll help on Apache 1.3 connector for TC 4.0 (If I could find more
> documentation)
I'm writing some documentation on the internals of the library and how to
write a module for your own web server, and trying to clean up the WARP
protocol specification (wich is very rough and absolutely undocumented)...
Pier
--
Pier P. Fumagalli Apache Software Foundation <mailto:[EMAIL PROTECTED]>
----------------------------------------------------------------------------
Neque porro quisquam est qui dolorem ipsum quia dolor sit amet, consectetur,
adipisci velit... (Cicero: "De Finibus" 1.10.32)
