| Oh, almost forget it... ASP is a loose of time on developer time... and
the
| module is to heavy, sorry but betwen oracle and ASP our server is down in
| performance, we run unix on a SGI and with 256mb ram...
| If you are trying to put ASP cause you donīt want to break the designer
| work, you are loosing your time (that was the intention here, but it
doesnīt
| work), the design is all broke.
| Is more estructured and I vote for put HTML into Perl and not Perl into
HTML
| or the same with ASP.
I think you have a point if you're writing stuff which is going to get a
million or so pageviews a day. In that case, you'll probably have a pretty
good insight in how things are going to be in advance and you can spent some
valuable time into thinking out every aspect of your application before you
actually start coding.
I think the big bonus of Apache::ASP (or one of the other embedded perl
implemententations) is that one can start working on a project with a very
ugly looking functional implementation of what you want and later add (or
let other people add) layout to it with their very nice HTML design tools
out there, like DreamWeaver and other kick-ass Macromedia products even I
like to work with. With Apache::ASP, I can work together with people who
have great skills in using visual HTML editors but think they see line-noise
when they actually see perl - as long as they leave the asp tags alone.
Before this, we had to develop the complete design of a website and then in
the end wrap the HTML in perl scripts. In case of any change in design or
restyle, everything had to be done all over and there I was cut/copy/pasting
everything all over.
In my opinion, using Apache::ASP instead of doing old fashioned scripts,
greatly reduces the time taken to complete a project, especially in those
cases where you have to work on something with a lot of people and you don't
know exactly what the finished project is going to be like until it's
actually finished. This indeed has some drawbacks in performance. But hey,
processor time is getting cheaper each day. If you're really aiming for
speed and performance, there's always the option of rewriting and optimizing
when your product is finished using non-embedded perl, C or, if you're a
real die hard, even ASM. I would prefer buying another Pentium box, though.
Except for some very busy sites, you'll probably don't care about a few
extra milliseconds. Selects on databases which have grown out of proportion
or have a bad structure were a far bigger slowdown than the use of
Apache::ASP in most things I've seen so far.
Now for the non rational part, consider this: just because Apache::ASP was
out there I was able to convince some of the most nasty M$ IIS-addicted
people I work with that Apache+Perl is a very good alternative for IIS. It
isn't that much of a change if people won't have to change their way of
thinking and can continue using their existing skills and tools to develop a
website. For most website developers switching from VBScript ASP to
PerlScript ASP is just a matter of learning some basic rules and grammar.
Consider this - rather unethical - issue too: The main problem I had with
people who are more into marketing then into technical stuff (say: managers)
is that every time I tried to convince them in using someting non-M$ for a
new project, I would have a terrible hard time. Thanks to Apache::ASP, I can
make them dream on while they see *.asp floating around all over the place,
but don't know what's really going on. Until the complete product has
proofed to work - and then suddenly they don't care anymore if they find out
there is no M$ box at the other end of the wire ;P
Bottomline: Apache::ASP made me really happy because now don't have to
develop for IIS anymore and I can stick to my Linux environment. I can
concentrate on real scripting and let other people without any scripting
knowledge focus on creating the HTML and layout.
Ime
