I should have added that I'm running on:
#Server: Apache/1.3.33 (Unix) mod_perl/1.29
Does that explain it right there? Maybe I don't have a handler
installed that comes with the mod_perl2 distro? Or does the
sameinterp stuff only run on mod_perl2?
I started to try to copy the tests over into my testing sandbox, but
it's slow going. There are many hooks into different modules in the
test tree. There are also a few calls in sameinterp.pm to Apache2
modules like Apache2::RequestIO and Apache2::Const.
Jim
On Aug 16, 2005, at 6:58 PM, Stas Bekman wrote:
Jim Brandt wrote:
I'm working on some code based on the example here:
<http://perl.apache.org/docs/general/testing/
testing.html#Hitting_the_Same_Interpreter__Server_Thread_Process_Inst
anc e_>
but I'm not getting a value back when I call same_interp_tie.
To try to debug, I pulled the code from same_interp_tie into my
code and I'm basically making this call directly and still
getting nothing back:
my $res = GET($arg_ref->{url}, 'X-PerlInterpreter', 'tie');
my $same_interp = $res->header('X-PerlInterpreter');
warn "value is>>$same_interp<<";
That gives me:
value is>><<
I'm basically using the stock test server, but I'm pointing to
our system apache binary and running on an alternate port.
Is it possible I'm missing something in my apache binary that's
preventing this from working? Any other things I can check?
Jim, have you checked the real tests? grep the modperl-2.0/t test
suite for examples.
--
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
==========================================
Jim Brandt
Administrative Computing Services
University at Buffalo
