Re: failing httpd-test tests

2004-08-11 Thread Stas Bekman
Joe Orton wrote: On Tue, Aug 10, 2004 at 09:56:12AM -0700, Stas Bekman wrote: Aha! Excellent, Geoff! Does it solve the problem by moving those default_module calls after getting httpd config? Moving the calls one line further on fixed it for me. OK to check in? (BTW your patch had whitespace

Re: failing httpd-test tests

2004-08-11 Thread Joe Orton
On Wed, Aug 11, 2004 at 01:17:04AM -0700, Stas Bekman wrote: I'd rather see it moved two statements (it still works, doesn't it?) so the eapi comes right after inherit_config. Otherwise, yes, please commit it. Yes, great, done. so are we all clean now? Any other problems? No failures with

Re: forcing full config in Makefile.PL (was Re: failing httpd-test tests)

2004-08-11 Thread Stas Bekman
Geoffrey Young wrote: As a result of my changes, now the API has two wrappers Apache::Test::config (full config as before), and Apache::Test::basic_config, which is the same sans httpd information. For example to autogenerate t/TEST and other files you don't need to know anything about httpd, and

Re: failing httpd-test tests

2004-08-11 Thread Stas Bekman
Joe Orton wrote: On Wed, Aug 11, 2004 at 01:17:04AM -0700, Stas Bekman wrote: I'd rather see it moved two statements (it still works, doesn't it?) so the eapi comes right after inherit_config. Otherwise, yes, please commit it. Yes, great, done. so are we all clean now? Any other problems? No

Re: failing httpd-test tests

2004-08-11 Thread Stas Bekman
Geoffrey Young wrote: But things are getting more and more fragile and dependant on each other indeed. right now a fresh checkout will not even run for me because I don't have an ssl-enabled apache to run against. this is not a minor issue, as I suspect I'm in the majority for normal users.

Re: failing httpd-test tests

2004-08-11 Thread Stas Bekman
Stas Bekman wrote: Geoffrey Young wrote: But things are getting more and more fragile and dependant on each other indeed. right now a fresh checkout will not even run for me because I don't have an ssl-enabled apache to run against. this is not a minor issue, as I suspect I'm in the majority

apr_off_t on linux i386

2004-08-11 Thread Brian Akins
apr_off_t gets defined as a long on linux i386 and an off_t on x86_64. apr_off_t used as a byte counter rolls over fairly quickly on i386. Suggestions? -- Brian Akins Senior Systems Engineer CNN Internet Technologies

Re: apr_off_t on linux i386

2004-08-11 Thread Joe Orton
On Wed, Aug 11, 2004 at 09:23:36AM -0400, Brian Akins wrote: apr_off_t gets defined as a long on linux i386 and an off_t on x86_64. apr_off_t used as a byte counter rolls over fairly quickly on i386. Suggestions? Stick with x86_64 :) Or use HEAD where apr_off_t is an off64_t on i386 too.

Re: apr_off_t on linux i386

2004-08-11 Thread Brian Akins
Joe Orton wrote: On Wed, Aug 11, 2004 at 09:23:36AM -0400, Brian Akins wrote: apr_off_t gets defined as a long on linux i386 and an off_t on x86_64. apr_off_t used as a byte counter rolls over fairly quickly on i386. Suggestions? Stick with x86_64 :) Wish i could :) Or use HEAD where

Re: apr_off_t on linux i386

2004-08-11 Thread Garrett Rooney
Brian Akins wrote: Or use HEAD where apr_off_t is an off64_t on i386 too. any plan to backport this? All my counters are rolling over :( That sounds like the kind of thing that would break binary compatability, so I imagine it won't be backported. -garrett

[PATCH] add test_config hook

2004-08-11 Thread Joe Orton
Any interest in this for HEAD? Patch below adds a test_config hook which allows modules to do extra checking when httpd is invoked with -t. The new -t -D DUMP_MODULES feature can be implemented this way rather than hooking into mod_so from server/main.c, which I think is slightly cleaner; it's

[proxy] New implementation ready for testing

2004-08-11 Thread Mladen Turk
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

ARM4 module for Apache 2, any interest?

2004-08-11 Thread Bill Stoddard
I've written a module to ARM4 instrument Apache 2. I'd like to donate this module to the ASF and ideally put it in the modules/experimental directory (or somewhere else in the ASF where we can place it under cvs control?). The ARM4 API headers are available from the Open Group website at

Re: ARM4 module for Apache 2, any interest?

2004-08-11 Thread Paul Querna
So, after a quick look at the website, it looks like ARM4 is some sort of SNMP on Steroids? Also, the License is quite important for any possibility of donating any module to the ASF I think that needs to be pinned down before any discussion can really move forward. Finally, can you explain

Re: [PATCH] add test_config hook

2004-08-11 Thread Paul Querna
On Wed, 2004-08-11 at 16:24 +0100, Joe Orton wrote: Any interest in this for HEAD? Patch below adds a test_config hook which allows modules to do extra checking when httpd is invoked with -t. The new -t -D DUMP_MODULES feature can be implemented this way rather than hooking into mod_so from

Re: ARM4 module for Apache 2, any interest?

2004-08-11 Thread William A. Rowe, Jr.
Doesn't some de minimis treatment through the incubator still apply? There are two templates, one for a full project's incubation, one for a lightweight pass through IP vetting. ++1 here for submission to the incubator as a new httpd instrumentation subproject. Also happy to help on the ppmc.

Re: [proxy] New implementation ready for testing

2004-08-11 Thread William A. Rowe, Jr.
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

Re: ARM4 module for Apache 2, any interest?

2004-08-11 Thread Paul Querna
On Wed, 2004-08-11 at 12:08 -0500, William A. Rowe, Jr. wrote: [..snip..] -1 on experimental - it needs to die :) Look how long it's taken to get cache stable. If that module was only placed in the main distro once it was fully complete, it would have been finished far sooner. In general,

Re: [AJP] proxy status

2004-08-11 Thread William A. Rowe, Jr.
At 02:15 PM 8/7/2004, Costin wrote: Now let's see how to get this in Apache2.0... Gonna try to make that happen, if I can somehow merge history (ick) It would be great if we would have at least one or 2 people who are committers in both projects. Since we can't propose Mladen in apache, maybe

Re: [proxy] New implementation ready for testing

2004-08-11 Thread William A. Rowe, Jr.
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

Re: [proxy] New implementation ready for testing

2004-08-11 Thread Mladen Turk
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

[OT] Survey about FS/OS developers

2004-08-11 Thread Frauke Lehmann
Sorry for any cross-posting! Hello, My name is Frauke Lehmann and I'm writing my master thesis about the social formation of free software/open source (FS/OS) developers. A questionnaire is one part of my research - besides interviews and observations. It would be really nice, if you supported

Re: APR 1.0? [Was: ARM4 module for Apache 2, any interest?]

2004-08-11 Thread William A. Rowe, Jr.
At 12:48 PM 8/11/2004, Paul Querna wrote: On Wed, 2004-08-11 at 12:08 -0500, William A. Rowe, Jr. wrote: [..snip-snip..] In general, new modules into 2.0 doesn't seem to make alot of sense since 2.2 will release before ApacheCon (straightforward goal, don't you think?.) I hope so, but at the

Re: [proxy] New implementation ready for testing

2004-08-11 Thread Graham Leggett
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

Re: [proxy] New implementation ready for testing

2004-08-11 Thread Mladen Turk
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

Re: [proxy] New implementation ready for testing

2004-08-11 Thread William A. Rowe, Jr.
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 :)

Re: [PATCH] add test_config hook

2004-08-11 Thread Justin Erenkrantz
--On Wednesday, August 11, 2004 4:24 PM +0100 Joe Orton [EMAIL PROTECTED] wrote: Any interest in this for HEAD? Patch below adds a test_config hook which allows modules to do extra checking when httpd is invoked with -t. The new -t -D DUMP_MODULES feature can be implemented this way rather than

Re: [proxy] New implementation ready for testing

2004-08-11 Thread William A. Rowe, Jr.
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 brought back

Re: ARM4 module for Apache 2, any interest?

2004-08-11 Thread Bill Stoddard
Paul Querna wrote: So, after a quick look at the website, it looks like ARM4 is some sort of SNMP on Steroids? Also, the License is quite important for any possibility of donating any module to the ASF I think that needs to be pinned down before any discussion can really move forward. The

Re: ARM4 module for Apache 2, any interest?

2004-08-11 Thread Bill Stoddard
Bill Stoddard wrote: Paul Querna wrote: So, after a quick look at the website, it looks like ARM4 is some sort of SNMP on Steroids? Also, the License is quite important for any possibility of donating any module to the ASF I think that needs to be pinned down before any discussion can really

Re: [proxy] New implementation ready for testing

2004-08-11 Thread Mladen Turk
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...

Re: ARM4 module for Apache 2, any interest?

2004-08-11 Thread Bill Stoddard
William A. Rowe, Jr. wrote: Doesn't some de minimis treatment through the incubator still apply? There are two templates, one for a full project's incubation, one for a lightweight pass through IP vetting. ++1 here for submission to the incubator as a new httpd instrumentation subproject. Also

Re: [proxy] New implementation ready for testing

2004-08-11 Thread Graham Leggett
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

RFE: ap_input_mode_t as bitflags

2004-08-11 Thread Glenn Strauss
I'm finding ap_input_mode_t very restrictive as a linear enum and would like to make it an enum of bitflags. If I put together a patch, what are the chances it will be accepted? It is for Apache 2.1/2.2 only, because it a) breaks binary compatibility by changing the ap_input_mode_t values b)

Re: [proxy] New implementation ready for testing

2004-08-11 Thread Graham Leggett
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

Re: RFE: ap_input_mode_t as bitflags

2004-08-11 Thread Justin Erenkrantz
--On Wednesday, August 11, 2004 5:16 PM -0400 Glenn Strauss [EMAIL PROTECTED] wrote: I'm finding ap_input_mode_t very restrictive as a linear enum and would like to make it an enum of bitflags. Please back up a bit. Why do you think the modes should be combined? -- justin

Re: ARM4 module for Apache 2, any interest?

2004-08-11 Thread Justin Erenkrantz
--On Wednesday, August 11, 2004 12:08 PM -0500 William A. Rowe, Jr. [EMAIL PROTECTED] wrote: Doesn't some de minimis treatment through the incubator still apply? There are two templates, one for a full project's incubation, one for a lightweight pass through IP vetting. ++1 here for submission

httpd-2.2 release roadmap v0.1

2004-08-11 Thread William A. Rowe, Jr.
Working backwards and allowing a little time for slip: Nov 1: Planned final RC tarball for release of 2.2.0 Oct 1: Code freeze of all new features in 2.1-dev (for a month till we branch head to 2.2.0 and bless HEAD as 2.3-dev) Thoughts? Bill

Re: [proxy] New implementation ready for testing

2004-08-11 Thread William A. Rowe, Jr.
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, or is it

Re: httpd-2.2 release roadmap v0.1

2004-08-11 Thread Andr Malo
* William A. Rowe, Jr. [EMAIL PROTECTED] wrote: Working backwards and allowing a little time for slip: Nov 1: Planned final RC tarball for release of 2.2.0 Oct 1: Code freeze of all new features in 2.1-dev (for a month till we branch head to 2.2.0 and bless HEAD as 2.3-dev)

[STATUS] (apache-1.3) Wed Aug 11 23:45:12 EDT 2004

2004-08-11 Thread Rodent of Unusual Size
APACHE 1.3 STATUS: -*-text-*- Last modified at [$Date: 2004/05/20 15:16:42 $] Release: 1.3.32-dev: In development 1.3.31: Tagged May 7, 2004. Announced May 11, 2004. 1.3.30: Tagged April 9, 2004. Not released. 1.3.29: Tagged October 24,

[STATUS] (httpd-2.0) Wed Aug 11 23:45:17 EDT 2004

2004-08-11 Thread Rodent of Unusual Size
APACHE 2.0 STATUS: -*-text-*- Last modified at [$Date: 2004/08/11 17:13:51 $] Release: 2.0.51 : in development 2.0.50 : released June 30, 2004 as GA. 2.0.49 : released March 19, 2004 as GA. 2.0.48 : released October 29, 2003 as GA.

[STATUS] (httpd-2.1) Wed Aug 11 23:45:21 EDT 2004

2004-08-11 Thread Rodent of Unusual Size
APACHE 2.1 STATUS: -*-text-*- Last modified at [$Date: 2004/04/27 22:09:17 $] Release [NOTE that only Alpha/Beta releases occur in 2.1 development]: 2.1.0 : in development Please consult the following STATUS files for information on related

Re: [AJP] proxy status

2004-08-11 Thread Costin Manolache
William A. Rowe, Jr. wrote: At 02:15 PM 8/7/2004, Costin wrote: Now let's see how to get this in Apache2.0... Gonna try to make that happen, if I can somehow merge history (ick) It would be great if we would have at least one or 2 people who are committers in both projects. Since we can't