William A. Rowe, Jr. wrote:
At 11:14 AM 8/11/2004, Mladen Turk wrote:
The connection pool enables reusing backend connections
and was build around apr_reslist. At the moment only the
proxy_ajp extensively uses this connection pool, with
performance slightly better then mod_jk.
I noticed one huge
Theo Schlossnagle wrote:
I haven't had the time lately, but you (all) are welcome to dissect the
mod_backhand (Apache 1.3) module and pull the resource collection and
decision making framework out and put in into mod_proxy for Apache 2.
I have been watching the commits to proxy, but haven't yet
Pier Fumagalli wrote:
What's wrong with:
ProxyPassReverse / http://localhost:/
ProxyPreserveHost On
RewriteMap hosts rnd:/opt/apache/conf/tables/hosts.map
RewriteRule "^/(.*)" "${hosts:live}/$1" [P,L]
It isn't very elegant though. Someone who is well versed in mod_rewrite
and regular expressio
Pier Fumagalli wrote:
On 11 Aug 2004, at 17:14, Mladen Turk wrote:
Hi all,
We've finished the initial development of extended mod_proxy.
Since the development took place at jakata-tomcat-connectors,
the source code can be found under ajp/proxy.
Here is the list of major features added:
3. Added new
On 11 Aug 2004, at 17:14, Mladen Turk wrote:
Hi all,
We've finished the initial development of extended mod_proxy.
Since the development took place at jakata-tomcat-connectors,
the source code can be found under ajp/proxy.
Here is the list of major features added:
3. Added new module proxy_balancer
Rainer Jung wrote:
Concerning session stickyness: is the following scenario possible with
your mod_proxy, at least in the future?e
We support a critical high load application which is running in a two
cell environment.
We replicate via TC cluster locally inside each cell (2 TCs) but not
over
Concerning session stickyness: is the following scenario possible with
your mod_proxy, at least in the future?
We support a critical high load application which is running in a two
cell environment.
We replicate via TC cluster locally inside each cell (2 TCs) but not
over the boundaries of the
At 01:37 PM 8/11/2004, William A. Rowe, Jr. wrote:
>At 01:03 PM 8/11/2004, Graham Leggett wrote:
>>
>>My plan is to start bringing it into httpd v2.1 from next week, assessing
>>how hard the backports to httpd v2.0 would potentially be. Is the history
>>kept in the tomcat connector tree enough, o
William A. Rowe, Jr. wrote:
Since it will take some time to assess that the changes and new features
are stable, v.s. dev quality, I believe it's sorta pointless to put extra energy
into the 2.0 backport. We won't compromise mod_proxy again in 2.0 after
its very slow crawl to some measure of stab
Mr./mrs. Moderator
I am a Turkish. I don't want those e - mails.
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!--- Begin Message ---
William A. Rowe, Jr. wrote:
That's something of a shame, because we lose the development
history importing the finished effort, and it was furthe
At 01:03 PM 8/11/2004, Graham Leggett wrote:
>William A. Rowe, Jr. wrote:
>
>>That's something of a shame, because we lose the development
>>history importing the finished effort, and it was further disappointing
>>that you didn't bring across the earlier cvs history so this branch
>>could be broug
Remy Maucherat wrote:
So compared to AJP, this gives what ?
Nothing regarding performance :)
Or you can use the https to connect to
the tomcat on the internet.
Q: is there session stickiness in HTTP ?
Yes.
Congratulations for improving on mod_jk performance :)
proxy_balancer:
Does it do session sti
Remy Maucherat wrote:
Q: is there session stickiness in HTTP ?
As I understood from the commits, stickiness is part of balancer, and
balancer is protocol independant, which would make the answer yes.
Am I understanding correctly?
Regards,
Graham
--
smime.p7s
Description: S/MIME Cryptographic Si
William A. Rowe, Jr. wrote:
That's something of a shame, because we lose the development
history importing the finished effort, and it was further disappointing
that you didn't bring across the earlier cvs history so this branch
could be brought back into httpd/modules/proxy with a complete
history
Mladen Turk wrote:
Hi all,
We've finished the initial development of extended mod_proxy.
Since the development took place at jakata-tomcat-connectors,
the source code can be found under ajp/proxy.
Here is the list of major features added:
1. AJP13 protocol support
2. Connection pool for threaded se
William A. Rowe, Jr. wrote:
We've finished the initial development of extended mod_proxy.
Since the development took place at jakata-tomcat-connectors,
the source code can be found under ajp/proxy.
I'm entirely +1 today for bringing it back into modules/proxy/ (it's
a c-t-r branch.) How you did
At 11:14 AM 8/11/2004, Mladen Turk wrote:
>The connection pool enables reusing backend connections
>and was build around apr_reslist. At the moment only the
>proxy_ajp extensively uses this connection pool, with
>performance slightly better then mod_jk.
I noticed one huge win - unless I'm misread
At 11:14 AM 8/11/2004, Mladen Turk wrote:
>We've finished the initial development of extended mod_proxy.
>Since the development took place at jakata-tomcat-connectors,
>the source code can be found under ajp/proxy.
That's something of a shame, because we lose the development
history importing the
Hi all,
We've finished the initial development of extended mod_proxy.
Since the development took place at jakata-tomcat-connectors,
the source code can be found under ajp/proxy.
Here is the list of major features added:
1. AJP13 protocol support
2. Connection pool for threaded servers
3. Added new
19 matches
Mail list logo
