Graham Leggett wrote:
Mladen Turk wrote:
Since we are (Henri and myself, not sure for JeanFrederic) not
httpd commiters, I'm not sure how the proxy_ajp will get maintained,
but we can always send patches :)
I'm quite happy to maintain the code, and can chase up any patches you
send through in the
I plan on doing a pretty thourough test as soon as I get access to the box
we will be using. Currently our network specialists are working to get the
front end Alteon load balancers working properly. We've been hampered by a
number of linux network issues that may yet take some time to resolve.
J
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
Jeffrey Burgoyne wrote:
The first one is this method as prescribed above does not seem to have a
failover mechanism, i.e. if connection to one server fails, then the next
in line is tried. This is quite important for mission critical
installations.
The second is that while pure randomness is bette
On 16 Aug 2004, at 12:49, jean-frederic clere wrote:
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.
H
I've been following the changes to mod_proxy and have been absolutely
estatic as to where everything is headed and what is being done. I've been
working with a very large client for two years changing their whole
architectuer and using an Apache front end employing mod_proxy to their
backend techno
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
On Aug 16, 2004, at 6:54 AM, 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
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
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
Mladen Turk wrote:
Since we are (Henri and myself, not sure for JeanFrederic) not
httpd commiters, I'm not sure how the proxy_ajp will get maintained,
but we can always send patches :)
I'm quite happy to maintain the code, and can chase up any patches you
send through in the mean time, if others d
William A. Rowe, Jr. wrote:
Never cross my mind that we'll need all those try-error-fix
commits back on the httpd cvs tree.
We actually like those - the next individual to say "wow - this fix is easy!"
can go back over history and say "grumf - they tried that in the first place"
:)
Question...
At 12:54 PM 8/11/2004, you wrote:
>Never cross my mind that we'll need all those try-error-fix
>commits back on the httpd cvs tree.
We actually like those - the next individual to say "wow - this fix is easy!"
can go back over history and say "grumf - they tried that in the first place"
:)
Quest
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
Graham Leggett wrote:
William A. Rowe, Jr. wrote:
I'm actually very excited that we can offer in the 2.2 release - this
really rocks. What you accomplished is very cool!
I'm entirely +1 today for bringing it back into modules/proxy/ (it's a
c-t-r branch.) How you did it makes this a non-trivial
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
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
22 matches
Mail list logo
