On Thu, 17 May 2001, brian moseley wrote:
> i think "application server" describes a system that
> does more than implementing a templating language.
er, that's not to diss anybody's software. everything on
that short list is great stuff. but i stand behind my
assertion. a (web) application server has more than
presentation layer functionality. it is a complete
application deployment environment. it's the same argument
that matt makes for axkit not being a content management
system but rather a building block for a cms. mason and
axkit could be vital components of an application server,
but it's false to label them as such themselves. i can't
speak to embperl or the other things on the list, cos i'm
not familiar with them.
check out enhydra enterprise
(http://enterprise.enhydra.org/). it has services for
logging, naming, distributed objects, session management
(through ejb), database access, transaction management,
presentation (jsp), application control (servlets),
management, authentication, authorization. all of these apis
are immediately available to application developers and
deployers in a consistent integrated fashion. this is not
"download 18 different components from cpan and mash them
all together" kind of setup. you can unjar the damn thing,
run a config script, and it's ready to run apps. there are
unified documentation and extensive sample applications.
the problem i'm interested in solving is how to provide
integrated components and consistent apis with this quantity
of functionality and level of sophistication in a perl
application server. i think it's still a long way away, but
it would be cool if i was proven wrong.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
