Perl/Apache Alternative to IIS/ASP

[Christopher 'Ducky' Chapin]

~sdpm~

I believe perl would give you a better library to work from than PHP. PHP
has a lot of web-based drop-ins, but if you really want to build
something, you have to write it yourself - perl is just better for that.

I'd suggest having a look at something like embperl
(http://perl.apache.org/embperl) or Mason (http://masonhq.com). Both are
built for embedding perl into html pages. I prefer Mason, it made more
sense to me first. =)

As far as transitioning, sorry I can't offer much help there. =/

-Chris

On Sat, 13 Oct 2001, Peter C. de Tagyos wrote:

> ~sdpm~
> Hey all.
> 
> I am pretty new to Perl, having primarily experience with MS platforms and
> products.  Currently, I use IIS/ASP/COM+/SQL Server to construct e-commerce
> web sites.  I wish to get away from the MS solution, for a multitude of
> reasons, and I am looking into how I might do this.
> 
> Replacing IIS with Apache is pretty straightforward, and using PHP or
> perl_mod instead of ASP is also a pretty easy transition.  However, I cannot
> seem to figure out what would be the Perl equivalent of my business objects
> running in COM+.  Right now, the sites I develop are 3-tier, with the web
> boxes running IIS/ASP, the biz boxes running objects in COM+, and the DB
> server running SQL2000.  This setup is nice because I can support several
> web boxes with the sole biz box and DB box.  From all that I have read, the
> Perl alternative seems to advocate putting Apache and the Perl business
> modules all on one box, with perhaps a DB hosted on another box.  This
> doesn't seem to be decoupled enough.
> 
> So I guess what I am really asking, is how do I build a multi-tier system
> using Apache, Perl, and other open-source products?  If such systems aren't
> necessary, why not?
> 
> I would appreciate any advice.  I have looked on several Perl websites, and
> there doesn't seem to be any sort of guide or whitepaper for moving from a
> MS solution to an open-source one.  I think that such a document would be
> very helpful- for developers interested in transitioning, and for the
> pointy-haired bosses they are trying to convince. Perhaps I will write such
> a thing once I figure it all out.  :)
> 
> Thanks!
> 
> Peter
> 
> ~sdpm~
> 
> The posting address is: san-diego-pm-list at hfb.pm.org
> 
> List requests should be sent to: majordomo at hfb.pm.org
> 
> If you ever want to remove yourself from this mailing list,
> you can send mail to <majordomo at happyfunball.pm.org> with the following
> command in the body of your email message:
> 
>     unsubscribe san-diego-pm-list
> 
> If you ever need to get in contact with the owner of the list,
> (if you have trouble unsubscribing, or have questions about the
> list itself) send email to <owner-san-diego-pm-list at happyfunball.pm.org> .
> This is the general rule for most mailing lists when you need
> to contact a human.
> 

~sdpm~

The posting address is: san-diego-pm-list at hfb.pm.org

List requests should be sent to: majordomo at hfb.pm.org

If you ever want to remove yourself from this mailing list,
you can send mail to <majordomo at happyfunball.pm.org> with the following
command in the body of your email message:

    unsubscribe san-diego-pm-list

If you ever need to get in contact with the owner of the list,
(if you have trouble unsubscribing, or have questions about the
list itself) send email to <owner-san-diego-pm-list at happyfunball.pm.org> .
This is the general rule for most mailing lists when you need
to contact a human.