Re: [Proxool-developer] Driver specific interfaces

[Bill H. <bi...@lo...>]

On Wed, 2004-03-24 at 21:41, Christian Nedreg=E5rd wrote:

> Phrooh!

!

> Why do you consider tying your code  to a self-produced interface tied
> to the currently exposed methods of a vendor spesific class to be more
> robust and maintainable than tying your code to a ProxoolFacade
> method?

That's not the point. By exposing the real connection people can really
easily call close() or prepareStatement() directly. (In fact, they are
quite likely to build Statements directly). Calling close() directly
loses the connection forever. Building a Statement that Proxool doesn't
know about stops Proxool resetting the connection correctly when it is
returned to the pool.=20

> Using Proxool facade saves you both the writing/maintaining of the
> interface and the extra configration.

I agree with you there. I'm cautious about the extra work involved.=20

And I agree that tying your code to a self-written interface rather than
the Oracle (or whatever) class is no better.

- Bill