just a very simple test that verifies that the documented technique works.
later on it may evolve to include a special A-T API if we ever add one.
Is it enought to do and also
&need_module(mod_usertrack.c) to determine if the usertrack mnodule is
installed, or is there someplace deeper within t
Christopher H. Laco wrote:
just a very simple test that verifies that the documented technique
works. later on it may evolve to include a special A-T API if we ever
add one.
Is it enought to do and also
&need_module(mod_usertrack.c) to determine if the usertrack mnodule is
installed, or is th
but most people won't have this module installed...
Installed, or loaded? I know the httpd.conf defaults to having that module
commented out, but the module itself should be around.
Maybe relying on Apache::Session would cover more install scnerios instead.
I was trying to avoid writing a custom
Christopher H. Laco wrote:
but most people won't have this module installed...
Installed, or loaded? I know the httpd.conf defaults to having that
module commented out, but the module itself should be around.
Loaded or even available...
Maybe relying on Apache::Session would cover more install sc
CChristopher H. Laco wrote:
>>> Maybe relying on Apache::Session would cover more install scnerios
>>> instead. I was trying to avoid writing a custom handler just to
>>> accept and toss some cookies in the test environment, but maybe
>>> that's better. At least then everyone install should be able
Christopher H. Laco wrote:
CChristopher H. Laco wrote:
>>> Maybe relying on Apache::Session would cover more install scnerios
>>> instead. I was trying to avoid writing a custom handler just to
>>> accept and toss some cookies in the test environment, but maybe
>>> that's better. At least then
Christopher H. Laco wrote:
Christopher H. Laco wrote:
CChristopher H. Laco wrote:
>>> Maybe relying on Apache::Session would cover more install scnerios
>>> instead. I was trying to avoid writing a custom handler just to
>>> accept and toss some cookies in the test environment, but maybe
>>> th
Stas Bekman wrote:
[snip]
Why don't you first post what you had on your mind. May be your idea
doesn't need that at all.
Well, here's what I was thinking. First, write a quick and dirty
mod_perl handler that looked for a specific cookie; let's say 'ApacheTest'.
If it wasn't supplied by the cli
Christopher H. Laco wrote:
Stas Bekman wrote:
[snip]
Why don't you first post what you had on your mind. May be your idea
doesn't need that at all.
Well, here's what I was thinking. First, write a quick and dirty
mod_perl handler that looked for a specific cookie; let's say 'ApacheTest'.
If it
Stas Bekman wrote:
Sounds good. Though it'll probably need to leave in the modperl2's test
suite and not Apache-Test's one. but let's see the code first and then
see where it's the best to apply it. You can use the
http://perl.apache.org/~geoff/Apache-Test-skeleton-mp2.tar.gz
to make it easy to w
Christopher H. Laco wrote:
Stas Bekman wrote:
Sounds good. Though it'll probably need to leave in the modperl2's
test suite and not Apache-Test's one. but let's see the code first and
then see where it's the best to apply it. You can use the
http://perl.apache.org/~geoff/Apache-Test-skeleton-mp2.
Stas Bekman wrote:
Christopher H. Laco wrote:
Stas Bekman wrote:
Sounds good. Though it'll probably need to leave in the modperl2's
test suite and not Apache-Test's one. but let's see the code first
and then see where it's the best to apply it. You can use the
http://perl.apache.org/~geoff/Apache
Michael Peters wrote:
Stas Bekman wrote:
Christopher H. Laco wrote:
Stas Bekman wrote:
Sounds good. Though it'll probably need to leave in the modperl2's
test suite and not Apache-Test's one. but let's see the code first
and then see where it's the best to apply it. You can use the
http://perl.ap
Stas Bekman wrote:
Michael Peters wrote:
Stas Bekman wrote:
Christopher H. Laco wrote:
Stas Bekman wrote:
Sounds good. Though it'll probably need to leave in the modperl2's
test suite and not Apache-Test's one. but let's see the code first
and then see where it's the best to apply it. You can use
Just because I'm like that. :-)
I noticed in A-T/t/redirect.t we have:
plan tests => 6, need_module('mod_alias.c') && &need_lwp;
Of course, I noticed this after skimming over the A-T pod again , where
it mentions:
It's also important to mention to avoid using:
plan
Christopher H. Laco wrote:
Just because I'm like that. :-)
I noticed in A-T/t/redirect.t we have:
plan tests => 6, need_module('mod_alias.c') && &need_lwp;
Of course, I noticed this after skimming over the A-T pod again , where
it mentions:
It's also important to mention to avoid using:
Christopher H. Laco wrote:
Just because I'm like that. :-)
I noticed in A-T/t/redirect.t we have:
plan tests => 6, need_module('mod_alias.c') && &need_lwp;
Of course, I noticed this after skimming over the A-T pod again , where
it mentions:
It's also important to mention to avoid using:
> -plan tests => 6, need_module('mod_alias.c') && &need_lwp;
> +plan tests => 6, need need_module('mod_alias.c'), &need_lwp;
^
?
:)
--Geoff
Geoffrey Young wrote:
-plan tests => 6, need_module('mod_alias.c') && &need_lwp;
+plan tests => 6, need need_module('mod_alias.c'), &need_lwp;
^
?
:)
--Geoff
Ha, now see what I've started. :-)
Geoffrey Young wrote:
-plan tests => 6, need_module('mod_alias.c') && &need_lwp;
+plan tests => 6, need need_module('mod_alias.c'), &need_lwp;
^
?
:)
Garbage in, garbage out :) now fixed :)
--
_
20 matches
Mail list logo
