Subject | RE: [IB-Java] Re: client-java driver pretty slow |
---|---|
Author | Paulo Gaspar |
Post date | 2001-11-26T22:49:02Z |
Hi David,
did not listen enough to Ceki Gulcu's (Log4J main contributor) critics and,
among other things, are keeping a strange set of Log Levels. For instance,
they have a lot of "debug" levels but only one error level, making no
distinction between a recoverable error and a fatal error.
This is quite strange considering that even the exception class hierarchy
makes this distinction, having an hierarchy of recoverable exceptions
descending from java.lang.Exception and another one of non-recoverable
exceptions descending from java.lang.Error. (java.lang.Error javadocs are
quite clear about this distinction.)
I think that Log4J has some adapters but I do not know them enough. Anyway,
what I am offering is something much lighter.
BTW, I also have a wrapper for the JDK 1.4 Log API.
dependencies.
mention somewhere it uses code from Apache.
Have fun,
Paulo Gaspar
http://www.krankikom.de
http://www.ruhronline.de
> This looks pretty interesting. I haven't looked at the progressThe main problem with the JDK 1.4 Log API was, last time I looked, that they
> of logging
> recently, I understand theres a Logger in jdk 1.4 and log4j has adapted in
> v 1.2 to be somewhat compatible. How does your stuff relate to these
> developments?
did not listen enough to Ceki Gulcu's (Log4J main contributor) critics and,
among other things, are keeping a strange set of Log Levels. For instance,
they have a lot of "debug" levels but only one error level, making no
distinction between a recoverable error and a fatal error.
This is quite strange considering that even the exception class hierarchy
makes this distinction, having an hierarchy of recoverable exceptions
descending from java.lang.Exception and another one of non-recoverable
exceptions descending from java.lang.Error. (java.lang.Error javadocs are
quite clear about this distinction.)
I think that Log4J has some adapters but I do not know them enough. Anyway,
what I am offering is something much lighter.
BTW, I also have a wrapper for the JDK 1.4 Log API.
> I'd like to take a look anyway. I guess since logging is used by all theOk. I will create a package with that name and clean the code of any
> packages we should put it in org.firebirdsql.logging?
dependencies.
> (I'm assuming you areYes, of course. Although part of this came from Apache so, we should just
> offering to contribute a version of your code to firebird?)
mention somewhere it uses code from Apache.
Have fun,
Paulo Gaspar
http://www.krankikom.de
http://www.ruhronline.de
> -----Original Message-----
> From: David Jencks [mailto:davidjencks@...]
> Sent: Monday, November 26, 2001 7:52 PM
> To: IB-Java@yahoogroups.com
> Subject: Re: [IB-Java] Re: client-java driver pretty slow
>
>
> This looks pretty interesting. I haven't looked at the progress
> of logging
> recently, I understand theres a Logger in jdk 1.4 and log4j has adapted in
> v 1.2 to be somewhat compatible. How does your stuff relate to these
> developments?
>
> I'd like to take a look anyway. I guess since logging is used by all the
> packages we should put it in org.firebirdsql.logging? (I'm
> assuming you are
> offering to contribute a version of your code to firebird?)
>
> Thanks!
>
> david jencks
>
> On 2001.11.26 13:33:52 -0500 Paulo Gaspar wrote:
> > I have a Common logger interface plus:
> > - Adapter for Apache Jakarta LogKit;
> > - Adpater for Log4J;
> > - Simple console log implementation;
> > (Realy easy to convert into a file implementation.)
> > - NoOp log implementation (does nothing for production).
> >
> >
> > The interface and the first 2 adapters are based on similar components
> > form the Apache Jakarta Avalon project, after stripping out the
> > Framework dependent bits.
> >
> > It is really simple and small code.
> >
> > Are you interested on this?
> > If yes, under what package name do you want it?
> >
> >
> > Have fun,
> > Paulo Gaspar
> >
> >
> > http://www.krankikom.de
> > http://www.ruhronline.de
> >
> >
> >
> > > -----Original Message-----
> > > From: Luca Lafranchi [mailto:luca.lafranchi@...]
> > > Sent: Monday, November 26, 2001 5:25 PM
> > >
> > >
> > > > 1. The amount of logging is still kind of ridiculous for production
> > > use. I
> > > > am very tempted to use log4j to make the amount of logging
> > configurable
> > > > while running. How much outcry would there be towards adding this
> > > library?
> > >
> > > No outcry at all (at least from me ;) ) But remember one thing: if
> > > this driver is to be used in an applet environment it should be fast
> > > downloadable: the more libraries you add, the bigger it becomes, the
> > > slower it will be to download. I don't use it in an applet
> > > environment, but others may want to...
> > >
> > >
> > > >
> > > > 2. To solve the "blob access outside of autocommit transaction"
> > problem,
> > > > how about putting each blob access in its own transaction (when
> > > autocommit
> > > > is happening)? I haven't looked but think this would be pretty easy
> > to
> > > > implement.
> > >
> > > Sorry, but I don't know much of driver implementation (shame
> on me!)...
> > >
> > > Good evening to all,
> > > Luca
> >
> >
> >
> > To unsubscribe from this group, send an email to:
> > IB-Java-unsubscribe@egroups.com
> >
> >
> >
> > Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
> >
> >
> >
> >
> >
>
>
> To unsubscribe from this group, send an email to:
> IB-Java-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>