Re^2: mod_perl2 design - what are the Ways To Do It ?

But some of the apache-specific modules haven't been ported yet... right? Question is, should I wait for the port, or just move my code to them when they are ported to perl6 ? (in other words, are they comming soon?)

perl -e'$b=unpack"b*",pack"H*","59dfce2d6b1664d3b26cd9969503";\
for(;$a<length$b;$a+=9){print+pack"b8",substr$b,$a,8;}'
[download]

My public key

Comment on Re^2: mod_perl2 design - what are the Ways To Do It ? Download Code

Replies are listed 'Best First'.
Re^3: mod_perl2 design - what are the Ways To Do It ? by hardburn (Abbot) on Jun 16, 2004 at 19:09 UTC
I don't see where Perl6 comes into it. Both branches of mod_perl are working off Perl5 and will probably continue to do so for some time. There is a mod_parrot project underway, though. IMHO, working at the Parrot level makes more sense, as it gives Apache integration with a bunch of other languages for free. You are correct that not all the old modules work on mod_perl2 yet. You need to ask yourself if you need to use any of the modules that don't currently work. If not, then go ahead and use mod_perl2. If so, you must either use mod_perl1, be willing to put effort into porting those modules, or wait. ---- send money to your kernel via the boot loader.. This and more wisdom available from Markov Hardburn.	[reply]
Re^4: mod_perl2 design - what are the Ways To Do It ? by yosefm (Friar) on Jun 17, 2004 at 09:34 UTC
I don't see where Perl6 comes into it I was trying tro make a joke about waiting for something indefinitely. Oh, well, maybe I should not persue a career in comedy... `perl -e'$b=unpack"b",pack"H","59dfce2d6b1664d3b26cd9969503";\ for(;$a<length$b;$a+=9){print+pack"b8",substr$b,$a,8;}'` [download] My public key	[reply] [d/l]