As long as the iffy stuff does not get boiled then it is fine.I meant
apache. Just as in GPL 3, who knows what apache decided to go with in
terms of licenses. If it stick to BSD then well then no need to worry
about IIS or any other web server(But I still think that shouldn't matter).
I think mod_perl should still stick to apache only. M$ people will never
may realizes what mod_perl would do for them. Just as what happened for
activestate perl. It never took off that well(I don't see that many
sites uses activestate perl with IIS though).
I think this thread has dragging endless string of countless matters.
Foo Ji-Haw wrote:
One of my hopes for mod_perl, is that it will evolve into a web
server-independent layer, that can be put on IIS as well (for example). I do
agree that Apache is a much stronger platform than IIS, but it is a bit iffy
to put all the eggs in the same basket...
----- Original Message -----
From: "Arne Skjaerholt" <[EMAIL PROTECTED]>
To: <modperl@perl.apache.org>
Sent: Thursday, February 16, 2006 11:11 PM
Subject: Re: A question for the newbies
I'm not exactly a newbie anymore, but I came to mod_perl by way of Perl
scripts for the shell. I'd already written some PHP, but when I learned
Perl I saw the error of my ways as it were and realized that PHP really
is quite the makeshift language and that developing in Perl was far more
comfortable (and better for my sanity =).
Also, once I understood what mod_perl was -really- about, I got all the
more excited as it opens up a host of possibilities not available in
PHP.
Arne
:wq
