"Erich L. Markert" wrote:
>
> > What I don't understand is *why*. Why can't you use to
> > independent pieces of software: one for templates and the other
> > for sessions that work perfectly well together (or seperately)?
> >
>
> Paul,
>
> I don't think anyone (certainly not myself) is suggesting that all other
> solutions be done away with - bigger is not always better. However, for
> certain types of projects an intergrated solution certainly offers up
> more appeal than trying to get all this disparate solutions to work in
> unison...
>
> I know, personally, that my last project(s) would have benefitted
> greatly from a integrated perl app server solution - especially if alot
> of the underlying technologies can be hidden from the less than
> technical folks...
I'll throw in my $0.02 and agree with Erich. We have twice as many HTML
people as perl programmers. So it was very important to make things as
simple as possible for them. The less they have to learn, the better. I
like to make my life as simple as possible... So a comprehensive app
server would go a LONG way in this regard.
I'll also say that I like the idea of plugging in different components
(Sessions, templating, etc) I need, when I need them, and where I need
them. There is also much to be said for flexibility. Not all our clients
will need/want/allow a mod_perl server. Perhaps their situation calls
for a $30/month shared hosting solution instead of mod_perl. This is
where the plug-in approach works best. We have both types of clients, so
choice is good. :-)
--
Drew Taylor
Vialogix Communications, Inc.
501 N. College Street
Charlotte, NC 28202
704 370 0550
http://www.vialogix.com/
