on 8/25/2000 3:35 AM, "Alex Reina London" <[EMAIL PROTECTED]> wrote:
> Dear Turbine followers,
> I am using Turbine as part of a project also involving Jetspeed�s
> implementation of iCalendar [RFC 2445].
>
> I do appreciate it has become a great framework and feel grateful to the
> people
> who have put their work in it. After having had a look at the TODO document,
> the wish list, etc I feel the time has come to do something about it.
Great!
> This is what I propose to undertake:
>
> - Housekeeping thread to return timed-out connections to the pool, it should
> also check for stale connections such as those that have caught an SQL warning
+1
> - Fail-safe mechanism as described somewhere in the code so that a backup
> RDBMS
> may be used if all connections to the default DB fail. The exact way this
> should work would require further thought
Yes, post a proposal to this list.
> - Better wrapping for the Connection class, including all its methods and,
> particularly, the ability to create other type of Statement objects
I need more details on this before I'm going to +1 it.
> - Abstract the log capabilities as a Turbine service and include a Factory
> class which can create logs for different services, with a pluggable back-end.
100% +1
> - Incorporate IBM Log4J package as the default back-end for the log service
100% +1
> I am not particularly interested in being granted cvs commit. Rather, I'll
> post
> the source somewhere reachable by everyone and if any commiter wishes to do
> so,
> they can be incorporated into the source tree.
>
> Any comments, thoughts, suggestions, anyone?
sounds great!
-jon
--
Scarab -
Java Servlet Based - Open Source
Bug/Issue Tracking System
<http://scarab.tigris.org/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
