Re: [RELEASE CANDIDATE] libapreq2 2.12 RC1
Hi Joe, I think that I discussed the following issue with Issac, two years ago. Actually, the idea to have an interactive fallback for CGI, was mine, I was the sponsor, and Issac programmed it (very well!). Before getting any decision, I want to discuss it again with him, which can't be done before Sunday: Currently, is_interactive_mode() is based on GATEWAY_INTERFACE, which is defined by any CGI query from the webserver (RFC). The second case is when a user runs it manually, so GATEWAY_INTERFACE is undefined, and the fallback is to get the params interactively. But there is a third case - When the user wants to feed QUERY_STRING manually. So if we test QUERY_STRING (rather than GATEWAY_INTERFACE), we support all the three cases, because QUERY_STRING is defined by any CGI query (even in POST - but with an empty content). I think this is going to be the first stable version with interactive mode, so it's the last opportunity to change this behavior. I want to re-check it. Regards, -- Eli Marmor mar...@netmask.it CEO, Netmask (El-Mar) Internet Technologies Ltd. __ Tel.: +972-9-766-1020 8 Yad-Harutzim St. Fax.: +972-9-766-1314 P.O.B. 7004 Mobile: +972-50-5237338 Kfar-Saba 44641, Israel
Re: [RELEASE CANDIDATE] libapreq2 2.12 RC1
- Original Message From: Eli Marmor mar...@netmask.it To: apreq-dev@httpd.apache.org Sent: Friday, March 6, 2009 10:12:44 AM Subject: Re: [RELEASE CANDIDATE] libapreq2 2.12 RC1 Hi Joe, I think that I discussed the following issue with Issac, two years ago. Actually, the idea to have an interactive fallback for CGI, was mine, I was the sponsor, and Issac programmed it (very well!). Before getting any decision, I want to discuss it again with him, which can't be done before Sunday: That's fine, but realize that there are other committers on this project whose votes towards a release count just as much as Issac's. If we get majority consensus on the candidate I cut, I intend to release it, with or without your's or Issac's approval. Currently, is_interactive_mode() is based on GATEWAY_INTERFACE, which is defined by any CGI query from the webserver (RFC). The second case is when a user runs it manually, so GATEWAY_INTERFACE is undefined, and the fallback is to get the params interactively. But there is a third case - When the user wants to feed QUERY_STRING manually. So if we test QUERY_STRING (rather than GATEWAY_INTERFACE), we support all the three cases, because QUERY_STRING is defined by any CGI query (even in POST - but with an empty content). I think this is going to be the first stable version with interactive mode, so it's the last opportunity to change this behavior. I want to re-check it. The folks who participate in this project have a terrible habit of waiting until a release candidate is cut before actually waking up, thinking about the consequences, and hollering bloody murder just because things don't look perfect on their favorite platform. I'm not saying we should lower our standards, but I am saying waiting to test drive apreq until it's release time is far too late in the game to be useful to us as a development community (and is why I continue to cut Release Candidates instead of final tarballs). With respect to the CGI interactive mode, the fact that we are even adding that into the cgi module itself means that we don't mind changing the behavior of that module within minor version bumps. Therefore changing it again after 2.12 is released is both realistic and likely to happen once we get some usage feedback on it. I'm not worried about getting it perfect the first time out of the gate, and I don't think any of the other committers on this project are either. YMMV.
Re: [RELEASE CANDIDATE] libapreq2 2.12 RC1
- Original Message From: Fred Moyer f...@silverliningnetworks.com To: Joe Schaefer joe_schae...@yahoo.com Cc: apreq-...@httpd.apache.org Sent: Friday, March 6, 2009 12:10:15 PM Subject: Re: [RELEASE CANDIDATE] libapreq2 2.12 RC1 Joe Schaefer wrote: Please test and vote on the following tarball and sigfile: http://people.apache.org/~joes/libapreq2-2.12-RC1.tar.gz http://people.apache.org/~joes/libapreq2-2.12-RC1.tar.gz.asc I've seeded the dates to be 1 week from today, so let's not dilly-dally please ;-) Getting an odd message on OS X but maybe it is my setup. OS X 10.5, mod_perl-svn, perl 5.8.8 unthreaded, httpd 2.2.4 make test: waiting 60 seconds for server to start: 00:00httpd: Syntax error on line 17 of /Users/phred/dev/svn/sl/trunk/SL-App/src/libapreq2-2.12/module/t/conf/httpd.conf: Cannot load /Users/phred/dev/svn/sl/trunk/SL-App/src/libapreq2-2.12/module/apache2/.libs/mod_apreq2.so into server: Library not loaded: /Users/phred/dev/sl/httpd2/lib/libapreq2.3.dylib That's the wrong library (it's an old installed version instead of the one from libapreq2-2.12/library/.libs). Check ldd (maybe oname IIRC) on mod_apreq2.so to see what the module is actually linked against. Referenced from: /Users/phred/dev/svn/sl/trunk/SL-App/src/libapreq2-2.12/module/apache2/.libs/mod_apreq2.so Reason: Incompatible library version: mod_apreq2.so requires version 11.0.0 or later, but libapreq2.3.dylib provides version 10.0.0
Re: [RELEASE CANDIDATE] libapreq2 2.12 RC1
Joe Schaefer wrote: Please test and vote on the following tarball and sigfile: http://people.apache.org/~joes/libapreq2-2.12-RC1.tar.gz http://people.apache.org/~joes/libapreq2-2.12-RC1.tar.gz.asc I've seeded the dates to be 1 week from today, so let's not dilly-dally please ;-) Getting an odd message on OS X but maybe it is my setup. OS X 10.5, mod_perl-svn, perl 5.8.8 unthreaded, httpd 2.2.4 make test: waiting 60 seconds for server to start: 00:00httpd: Syntax error on line 17 of /Users/phred/dev/svn/sl/trunk/SL-App/src/libapreq2-2.12/module/t/conf/httpd.conf: Cannot load /Users/phred/dev/svn/sl/trunk/SL-App/src/libapreq2-2.12/module/apache2/.libs/mod_apreq2.so into server: Library not loaded: /Users/phred/dev/sl/httpd2/lib/libapreq2.3.dylib Referenced from: /Users/phred/dev/svn/sl/trunk/SL-App/src/libapreq2-2.12/module/apache2/.libs/mod_apreq2.so Reason: Incompatible library version: mod_apreq2.so requires version 11.0.0 or later, but libapreq2.3.dylib provides version 10.0.0
