Other than the JSP part, this isn't a real dichotomy. You can use J2EE and
EJBs behind a site hosted on Turbine, with your modules calling into this
layer for enterprise data and business logic. Turbine is just about
presentation and interaction management (mostly), the View and some of the
Controller layer in an MVC architecture.
-----Original Message-----
From: Carl Ludewig [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 27, 2000 11:19 AM
To: 'Turbine'
Subject: Would Like to Use Turbine
Hi Everyone,
I'm in charge of selecting the technology for a new web system at AudioBase.
I'm
inclined to use Turbine, and was wondering if someone could answer a
question
for me. The marketing and management folks have heard a lot of the hype
surrounding J2EE, JSP & EJBs. Can someone make a compelling argument that
would
go over well with business types on why we should ignore the 'enterprise
standard' promoted by Sun and use Turbine. Jason Hunter has provided a good
argument for using WebMacro or Velocity, so I guess I'm really looking for
why
Turbine is better than EJB solutions provided by others. You don't need to
convince me as a programmer. I'm looking for reasoning that would appeal to
the
biz types.
Much Thanks,
Carl
--
Carl Ludewig
Director of Research & Development
AudioBase, Inc.
(415) 389-6875
[EMAIL PROTECTED]
http://www.audiobase.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
