You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Colleen <co...@darksideproductions.net> on 2002/03/29 00:53:23 UTC
RE: ezmlm response
When using Turbine in combination with either JSPs or a templating
engine, I realize that there are benefits such as the collection
of code into one location and the ability to re-use components, but
what are there detriments? For example, do processes take longer
because it's one extra step?
Is Turbine compatible with MySQL?
--colleen
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: ezmlm response
Posted by Eric Dobbs <er...@dobbse.net>.
On Thursday, March 28, 2002, at 04:53 PM, Colleen wrote:
> When using Turbine in combination with either JSPs or a templating
> engine, I realize that there are benefits such as the collection
> of code into one location and the ability to re-use components, but
> what are there detriments? For example, do processes take longer
> because it's one extra step?
Performance questions are notoriously hard to answer concretely.
Everything depends on your specific application. You're basically
stuck measuring for yourself with your own application.
The question you should be asking is "will Turbine make our
application easier to maintain and change as our business needs
grow and change?" The answer to that question is "yes".
> Is Turbine compatible with MySQL?
yes.
-Eric
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>