on 12/27/2000 11:20 AM, "Marcelo Vanzin" <[EMAIL PROTECTED]> wrote:
> In our pool our conections implement java.sql.Connection, and they wrap
> the real connection, giving access to all methods (doing some check to
> see if the connection is available or not), except the close(), which
> does nothing. :-) Only the pool can access the close() method of the
> real connection.
>
> This makes things easier when testing our classes outside of the web
> server. I just open a connection in a main() method and call the exact
> same class. (We do not use Turbine because I think when we began this
> Turbine was still not available, or at least I had never heard about,
> and now it would be too much work to migrate things).
Again, this stuff is already easy within Turbine and there is no need to
have it implement that interface.
> On a side note, our system uses a very simple templating engine I wrote,
> that is pretty bare-bones, but fast, and has everything we need here
> (keyword substitution, including of other templates, loops and ifs).
> Could be something to contribute also. :-)
I don't think that you need to contribute the whole template engine as we
already have one that is plenty fast (Velocity), but it would be cool to
contribute a Service that integrates it into Turbine and then you make the
template engine available yourself. :-)
thanks!
-jon
--
Honk if you love peace and quiet.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
