You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@velocity.apache.org by Francisco Hernandez <xy...@earthlink.net> on 2001/04/26 07:26:22 UTC
Turbine with Velocity?
Do you guys use Turbine with your Velocity powered web apps?
if so, how do you like it?
Re: Turbine with Velocity?
Posted by Francisco Hernandez <xy...@earthlink.net>.
Wow, seems like Turbine does alot.
By looking at the Turbine site I wasnt exactly sure what Turbine did but
looking back now it seems like a collection of many different packages/libs.
Im coming from PHP background and getting into more serious Java server-side
stuff. Thanks for your input!!
On Thursday 26 April 2001 12:09 am, you wrote:
> Hi Francisco,
>
> I use Velocity for a range of apps (some for clients, and some for my own
> use). Some of them aren't even web apps.
>
> With web apps we use Velocity + Turbine which is a winner. Turbine not
> only provides you with a structure for a Velocity app, but it gives you a
> lot of other useful web app services like db connection pooling, caching,
> db object-model, scheduler, XSL transformations, file-uploading, and a
> bunch I can't even remember.
>
> Turbine's services architecture won't load those that you don't use, so you
> needn't worry that all the stuff will slow your app down. It is rather
> nice to have a service handy (they're loaded automatically when you ask for
> them) for almost every web app task - gives you more time to concentrate on
> your actual application.
>
> ~ Leon
>
> > Do you guys use Turbine with your Velocity powered web apps?
> > if so, how do you like it?
Re: Turbine with Velocity?
Posted by Leon Messerschmidt <le...@opticode.co.za>.
Hi Francisco,
I use Velocity for a range of apps (some for clients, and some for my own
use). Some of them aren't even web apps.
With web apps we use Velocity + Turbine which is a winner. Turbine not only
provides you with a structure for a Velocity app, but it gives you a lot of
other useful web app services like db connection pooling, caching, db
object-model, scheduler, XSL transformations, file-uploading, and a bunch I
can't even remember.
Turbine's services architecture won't load those that you don't use, so you
needn't worry that all the stuff will slow your app down. It is rather nice
to have a service handy (they're loaded automatically when you ask for them)
for almost every web app task - gives you more time to concentrate on your
actual application.
~ Leon
> Do you guys use Turbine with your Velocity powered web apps?
> if so, how do you like it?
>