Re: New to ModPerl 2

I've used the following for about 6 months without any problem for reading cookies: # just copied all Apache related "use", not all needed for the sample code below of course use Apache::Connection; use Apache::RequestRec (); use Apache::RequestIO (); use Apache::Request(); use APR::Brigade ();

Re: New to ModPerl 2

I'm just wondering how people have handled cookie stuff before -- There seems to be a group that has encountered this error, and another group that has not -- if anyone is a member of the latter group and can share their approach to cookie/request handling (assuming its more than just substitut

Re: New to ModPerl 2

jonathan vanasco <[EMAIL PROTECTED]> writes: > On Nov 15, 2004, at 11:18 AM, Joe Schaefer wrote: [...] >> Can you please show us the code which segfaults? [...] > sub handler > { > my $r = shift; > my $req= Apache::Request->new( $r , DISABLE_UPLOADS=>1); >

Re: New to ModPerl 2

Assuming this is a segfault, i get the same error: [Tue Nov 16 00:45:17 2004] [notice] child pid 2237 exit signal Bus error (10) The only difference is the env variable to ApacheCookie This works: == #file:MyApache/Rocks.pm #-- package MyApache::Rocks;

Re: New to ModPerl 2

Kurt Hansen <[EMAIL PROTECTED]> writes: [...] > A few things that caused me more pain than I care to admit: > > 1. Apache::Cookie v2 requires an Apache::RequestRec environment > variable instead of an Apache::Request variable. Using the latter > caused a segmentation fault. If so, that's reall

Re: New to ModPerl 2

On Nov 14, 2004, at 7:04 PM, Dan Brian wrote: I'll add to your list (of potential confusion) that $r->args may not produce the expected results, and not just because of the change away from array context described at:

Re: New to ModPerl 2

On Nov 14, 2004, at 4:06 PM, Kurt Hansen wrote: Markus Wichitill wrote: Apache::Request 2.0 (libapreq2), like mod_perl 2.0, is officially still in development, but mostly done. http://httpd.apache.org/apreq/ I second the advice to use libapreq2 if your code is based on libapreq1. I'm almost done

Re: New to ModPerl 2

Note, though, that libapreq2 will require some changes in your code, but probably less than not using libapreq. Be sure to read the documentation, especially the notes about converting from v1, for Apache::Request and Apache::Cookie at: I'll add to your list (of potential confusion) that $r->

Re: New to ModPerl 2

Markus Wichitill wrote: jonathan vanasco wrote: In mod_perl1, I have a handler that takes an apache request object manipulates the cookie/session data into a user, then presents the user with a page in mod_perl2, however, there is no Apache::Request (yet) -- so my code simply doesn't work at al

Re: New to ModPerl 2

Markus Wichitill wrote: jonathan vanasco wrote: In mod_perl1, I have a handler that takes an apache request object manipulates the cookie/session data into a user, then presents the user with a page in mod_perl2, however, there is no Apache::Request (yet) -- so my code simply doesn't work at al

Re: New to ModPerl 2

jonathan vanasco wrote: In mod_perl1, I have a handler that takes an apache request object manipulates the cookie/session data into a user, then presents the user with a page in mod_perl2, however, there is no Apache::Request (yet) -- so my code simply doesn't work at all. Apache::Request 2.0

Re: New to modperl

On Tue, 2004-10-12 at 15:46, steve silvers wrote: > The scripts seem to run atleast 5 times > faster, maby just because I'm on Linux now. It could be all kinds of things, but a 5 times speedup is not unusual for mod_perl. > My question is how do I know if my scripts are running as modperl? Is th

Re: New to modperl

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Inspect $ENV{MOD_PERL} Better to Google for basic answers to questions like these. Also, the docs for mod_perl are excellent and have been for years. Additionally, the O'Rielly mod_perl (Eagle) book is tre