--- Jon Stevens <[EMAIL PROTECTED]> wrote:
> on 2/7/01 10:56 AM, "Morgan Delagrange"
> <[EMAIL PROTECTED]> wrote:
>
> > From their home pages, you wouldn't
> > even know that they featured database pooling.
>
> Absolute bullsh*t.
>
> The Turbine homepage *clearly* states:
>
> "The point of Turbine is to collect that code into
> one location and make it
> easy to create re-usable components (such as
> ParameterParsing, Database
> Connection Pools, Job Scheduling, GlobalCaches,
> integration with other tools
> such as Castor, Velocity, Webmacro, etc...) all
> under a license (Apache)
> that allows you to create useful websites for your
> customers without
> worrying about viral code. Turbine is not the end
> all answer, but it sure is
> a nice way to make your development life easier."
My mistake, although stating that you have a database
connection pool component does not imply that it is
applicable outside of Turbine.
> The #2 item on the left side navigation on every
> single Turbine page is the
> "features" document...
>
> <http://java.apache.org/turbine/features.html>
>
> "Singleton based Database Connection Pool (JDBC)
> with built in support for
> all of the major databases"
Same issue here as above. Pretend that I'm not
steeped in Turbine lore. How am I to know that I can
use this elsewhere?
> I'm sorry, but I'm tired of people claiming
> ignorance when there is clear
> documentation to the contrary. I'm also tired of
> other projects refusing to
> work with Turbine when Turbine has clearly been the
> leader in this area for
> over 2 years now.
>
> I also want to point out that Connection pools are
> more than just Connection
> pools, they also store information *about* the
> specific type of database
> that you are connecting to such as what type of SQL
> must be used to retrieve
> the last inserted id. This is something that Turbine
> depends on and I would
> make as a requirement that these features are
> available.
>
> Now, feel free to create yet another project to
> house this Connection
> Pooling code, but I *refuse* to work with that
> project until I see others
> doing so first.
I'm thrown off by your charter:
Turbine is a servlet based framework that
allows experienced Java developers to quickly
build secure web applications.
If I'm building a project that is not a web
application, why would I even investigate the features
of Turbine? Let's review the best connection pooling
mechanism (maybe Turbine, maybe Struts or some
spinoff) and create a generic utilities project to
house it. It's lame to have to include all the
Turbine classes just to get at something as low-level
as database pooling.
- M
=====
Morgan Delagrange
Britannica.com
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - Buy the things you want at great prices.
http://auctions.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
