Re: Few Important Questions
Mustafa Tan wrote: Hi Everybody, mod_perl is a great software. Thanks for everybody who spent time on it and make it available. When you send a reply to this, can you also describe how we can help, as an individiual, to support mod_perl and people behind it financially. Mustafa, one way to provide financial support is a donation: http://www.apache.org/foundation/contributing.html There's a paypal button on that page, and an address for sending checks. The ASF is a non profit org which makes donations tax deductible. mod_perl relies on the ASF infrastructure for its CVS server, mailing lists and web sites. Donations help fund these infrastructure expenses. Thanks! -- Eric Cholet
mod_perl compile options
All Can someone please tell me if the following compile time options will work without inherited (intermitted) problems. Btw. I'm running perl 5.8.0 and apache 1.3.27 (without lfs). % perl Makefile.PL \ USE_APXS=1 \ WITH_APXS=/usr/local/apache/bin/apxs \ EVERYTHING=1 \ PERL_USELARGEFILES=0 % make % make install I'm specifically interested in the **PERL_USELARGEFILES=0** option, can I rely on this (work-a-round)? Thanks for everyone's patience with me. Jaco Greyling Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.
RE: non-LFS Apache 1.3.27 w/ LFS Perl 5.8.0 (using mod_perl)
Guys Everything you've said so far make complete sense (thanks for that!). My question now is, did Doug take this into consideration when he build mod_perl v1.27 (w/ PERL_USELARGEFILES=0) and somehow wrote a function that cleans up the data structures from perl? I think I need someone with 'inside information' into mod_perl to comment on this one... Thx again, Jaco Greyling -Original Message- From: Ged Haywood [mailto:[EMAIL PROTECTED] Sent: 18 June 2003 14:53 To: Greyling, Jaco Cc: [EMAIL PROTECTED] Subject: RE: non-LFS Apache 1.3.27 w/ LFS Perl 5.8.0 (using mod_perl) Hi Jaco, On Wed, 18 Jun 2003 [EMAIL PROTECTED] wrote: As you can see it suggests rebuilding mod_perl with $PERL_USELARGEFILES=0 (which we do) so according to him it will work? Well it's in the list of suggestions, I don't think that's quite the same thing... I guess the bit about nobody listening to the warning is at least as relevant. :) If none of your system is configured to use large file offsets that's fine. It's when you choose to link together different parts, some of which do and some don't that I'd worry. Structure (mis)alignment can cause all kinds of subtle problems, some very obvious and some not, and the more you play with additional modules, interfaces to the Perl guts etc., the more likely you are to come across them before anyone else does. Traditionally the advice is even that you should use the same compiler to build Perl and mod_perl, for exactly this reason. I would always want to make sure that my Perl and mod_perl were both compiled the same way. 73, Ged. Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.
RE: non-LFS Apache 1.3.27 w/ LFS Perl 5.8.0 (using mod_perl)
Hi there, On Thu, 19 Jun 2003 [EMAIL PROTECTED] wrote: My question now is, did Doug take this into consideration when he build mod_perl v1.27 (w/ PERL_USELARGEFILES=0) I'm sure Doug took into consideration all sorts of things we never even thought about. Try it out and let us know what happens? I think I need someone with 'inside information' into mod_perl Well you have the source code... :) 73, Ged.
RE: non-LFS Apache 1.3.27 w/ LFS Perl 5.8.0 (using mod_perl)
Hey I found this link on the net and it seems to answer my question (right at the bottom), http://www.gossamer-threads.com/archive/mod_perl_C1/dev_F4/uselargefiles_P3969/ Thanks to all who contributed to my query... Jaco Greyling -Original Message- From: Ged Haywood [mailto:[EMAIL PROTECTED] Sent: 19 June 2003 14:45 To: Greyling, Jaco Cc: [EMAIL PROTECTED] Subject: RE: non-LFS Apache 1.3.27 w/ LFS Perl 5.8.0 (using mod_perl) Hi there, On Thu, 19 Jun 2003 [EMAIL PROTECTED] wrote: My question now is, did Doug take this into consideration when he build mod_perl v1.27 (w/ PERL_USELARGEFILES=0) I'm sure Doug took into consideration all sorts of things we never even thought about. Try it out and let us know what happens? I think I need someone with 'inside information' into mod_perl Well you have the source code... :) 73, Ged. Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.
module ported and doc addition...
Hi! Just wanted to let everyone know that I have just finished porting the Apache-AuthExpire module to work with both modperl1 and 2. It is a: # Small mod_perl handler to provide Authentication phase time outs for # sensitive areas, per realm. There are some issues with konqueror, mozilla and netscape, but should be a simple fix if someone is watching the headers Possible documentation inclusion...?: When using a ternary conditional in conjunction with a conditional operator, I needed to enclose the statement with parentheses to force the ternary conditional to be executed first. For example: my ($res, $sent_pw) = $r-get_basic_auth_pw; return $res if $res != (MP2 ? Apache::OK : Apache::Constants::OK); # return not OK status if not OK Took me a while to catch that... :P speeves cws
Re: module ported and doc addition...
Shannon Eric Peevey wrote: Hi! Just wanted to let everyone know that I have just finished porting the Apache-AuthExpire module to work with both modperl1 and 2. It is a: # Small mod_perl handler to provide Authentication phase time outs for # sensitive areas, per realm. There are some issues with konqueror, mozilla and netscape, but should be a simple fix if someone is watching the headers Possible documentation inclusion...?: When using a ternary conditional in conjunction with a conditional operator, I needed to enclose the statement with parentheses to force the ternary conditional to be executed first. For example: my ($res, $sent_pw) = $r-get_basic_auth_pw; return $res if $res != (MP2 ? Apache::OK : Apache::Constants::OK); # return not OK status if not OK Took me a while to catch that... :P speeves cws Is J. J. Horner on this list? (Are you out there...? :)) ) If so, can you contact me about getting permissions to upload the Apache-AuthExpire mod that I have ported? (So it can be indexed by PAUSE.) Also, Stas, is there a way that I can get around having to wait for an author to upload a ported module? I am not adding any functionality except making it work with both versions of modperl, and making additions that the CPAN testers have requested. I have a clear window for now, and would like to keep on porting mods while I have a little extra time... Thanks! speeves cws
Socket-based porotocol module: how to re-use connection?
Hi All, I am playing with a socket-based protocol module based on Stas' MyApache::EchoSocket. I wonder what is needed to enable the function of re-using connections? In perl we can use this: $server = IO::Socket::INET-new(LocalHost = my.host.com, LocalPort = 8899, ReuseAddr = 1, Proto = tcp, Listen= 200 ) How is this implemented http in mod_perl via Apache2 without using http? Any suggestions? Regards, Jie
[ANNOUNCE] libapreq-1.2 release
libapreq-1.2.tar.gz (Apache::Request) is now on CPAN: file: $CPAN/authors/id/J/JO/JOESUF/libapreq-1.2.tar.gz size: 277549 bytes md5: ae08726f11ca25a215d4d854d675c3ff and at www.apache.org: file: http://www.apache.org/dist/httpd/libapreq-1.2.tar.gz sig: http://www.apache.org/dist/httpd/libapreq-1.2.tar.gz.asc key: http://www.apache.org/dist/httpd/KEYS -- Changes since v1.1: =over 4 =item 1.2 - June 19, 2003 libapreq-1.2 released. =item 1.16 - June 19, 2003 Updated INSTALL README documents to explain how to configure the tests. Apache::Test v1.03 is now a prerequisite for libapreq. =item 1.15 - June 13, 2003 Experimental support for SFIO is withdrawn. =item 1.14 - April 30, 2003 Add documentation for subclassing Apache::Request. [Steve Hay] =item 1.13 - April 18, 2003 Sync test suite uris with latest Apache::Test [Stas] Patch mfd parser's Content-Disposition header to do case-insensitive matches on name filename keywords. This feature allows uploads from Nokia Series 60 phones to work as expected. [Oskari 'Okko' Ojala] Patch Request.xs to revert to using pre-1.1 $upload-fh code for pre-5.8 perls. This patch may get backed out prior to 1.2's release, unless it is known to resolve problems (zombies?) reported to occur with libapreq-1.1 uploads and pre-5.8 perls. [Joe] =item 1.12 - February 27, 2003 do a better mod_perl version checking, including the test for mod_perl 2.0. [Stas] Applied IKEBE Tomohiro's patch for handling %u strings. =item 1.11 - February 27, 2003 Add req-nargs to C API to distinguish between query string and request body params.
RE: MS SQL Server
I found FreeTDS and DBD::Sybase to be the best for me rather than the SQL Server with unixODBC setup which is difficult to setup, buggy and speed issues for me. As for the nonsense about Windows vs. Linux, it's about the best technology for the job. Sometimes people have two products they want to connect; let's not be lame about it. ~Ben -Original Message- From: Matt Sergeant [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 18, 2003 9:32 AM To: FARRINGTON, RYAN Cc: 'Andy Wardley'; [EMAIL PROTECTED] Subject: RE: MS SQL Server On Wed, 18 Jun 2003, FARRINGTON, RYAN wrote: omg... linux people using MS SQL servers? shame on you... =) I hold in one hand the option of taking a pager home with me. In the other hand is using MS SQL Server and giving support over to our 24/7 DBAs. Which would you choose? -- !-- Matt -- :-get a SMart net/:- Spam trap - do not mail: [EMAIL PROTECTED]
RE: MS SQL Server
I was making a joke... I'm the last person to knock on either platform considering I manage both =( every platform has it's purpose =) -Original Message- From: Davis, Benjamin [mailto:[EMAIL PROTECTED] Sent: Thursday, June 19, 2003 8:30 PM To: '[EMAIL PROTECTED]' Subject: RE: MS SQL Server I found FreeTDS and DBD::Sybase to be the best for me rather than the SQL Server with unixODBC setup which is difficult to setup, buggy and speed issues for me. As for the nonsense about Windows vs. Linux, it's about the best technology for the job. Sometimes people have two products they want to connect; let's not be lame about it. ~Ben -Original Message- From: Matt Sergeant [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 18, 2003 9:32 AM To: FARRINGTON, RYAN Cc: 'Andy Wardley'; [EMAIL PROTECTED] Subject: RE: MS SQL Server On Wed, 18 Jun 2003, FARRINGTON, RYAN wrote: omg... linux people using MS SQL servers? shame on you... =) I hold in one hand the option of taking a pager home with me. In the other hand is using MS SQL Server and giving support over to our 24/7 DBAs. Which would you choose? -- !-- Matt -- :-get a SMart net/:- Spam trap - do not mail: [EMAIL PROTECTED]
Re: [ANNOUNCE] libapreq-1.2 release
Joe Schaefer [EMAIL PROTECTED] writes: [...] and at www.apache.org: file: http://www.apache.org/dist/httpd/libapreq-1.2.tar.gz sig: http://www.apache.org/dist/httpd/libapreq-1.2.tar.gz.asc Correction- those urls for libapreq-1.2 should read http://www.apache.org/dist/httpd/libapreq/libapreq-1.2.tar.gz http://www.apache.org/dist/httpd/libapreq/libapreq-1.2.tar.gz.asc -- Joe Schaefer
