on 1/16/00 7:27 PM, george stewart <[EMAIL PROTECTED]> wrote:
> Jon, I don't agree with this. The major reason for
> the confusion is that you have OPL as an appendage of
> Turbine. Definitely, this isn't to the benefit of a
> wider audience of OPL users.
Why not?
> No, you don't need to
> superglue OPL to turbine. The difficulty in using
> Turbine's connection pooling with the broker manager
> is mostly to do with problems in the design of
> Turbine's broker manager. It's a broker manager,
> dbconnection, and pooling code all wrapped together.
> This really makes it unusable for other projects like
> OPL.
Why exactly is it unusable?
> You might want to rethink that design. For
> example, you use information like the timestamp in the
> dbconnection class to control the connection pooling.
> This is patently wrong.
Why is that wrong? How else do you propose expiring connections after a
certain amount of time?
> Any other connection broker
> gives you a jdbc connection. All of the information
> for managing the connection should be internal to the
> broker. Not handed to the user.
Exactly what difference does it make to hand the user a DBConnection or a
JDBC connection?? A DBConnection is just a wrapper around the JDBC
connection. Big fucking deal.
> There are better ways of dealing with this.
> Definitely, many of the fuctions in the persistence
> broker should be moved to the db connection class.
> Then exceptions can be handled when they percolate up
> to the user. I believe it's probably best for
> dbconnection to hold a reference to the broker so it
> can return itself to the broker in a finalize if the
> user fails to return it.
We are not talking about catching the exceptions. We are talking about
making sure that the connection is closed. So far, your code doesn't do any
of that.
> At this point, you probably shouldn't pollute the
> other turbine code with opl junk. Your most recent
> changes required opl to be compiled with the
> distribution of turbine. Why couldn't you work with
> your own copy? What was the benefit of adding this to
> Turbine.java?
>
> - george
The benefit is that we can have a MFC style servlet library that will
perform the way that we want it to and be feature complete.
-jon
--
Come to the first official Apache Software Foundation
Conference! <http://ApacheCon.Com/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
