> I would not  expect SLF4J to evolve much beyond  its current state but
> unfortunately  it's  not  something  I  could guarantee.  As  for  the
> ULogger -> Logger change,  please note that  it would have  been handled
> quite differently had log4j 1.2.10 were officially endorsed.

How would it have been handled differently?  Why should it be handled
differently if the interfaces are expected to evolve?  Use the freedom while
you have it.

> 
> 
> >- There are also at least two possible goals for an slf4j implementation
> >within log4j 1.2:
> >
> >  1) Provide an implementation of the slf4j interface in the latest
> > version of log4j 1.2.
> >  2) Provide an implementation of the slf4j interface that is compatible
> > with all 1.2.X versions of log4j.
> >
> >These goals suggest different approaches and implementations (direct vs
> >facade).
> 
> The term "facade" maybe a little ambiguous here. Did you mean "direct"
> vs "wrapping"?
> 
> Wrapping  is non-intrusive  while  a direct  implementation creates  a
> dependency. A  direct implementation allows for a  simpler, leaner and
> more  robust code  but  with all  the  inconveniences associated  with
> having an extra-dependency.

Wrapping is probably a better description, but would need to see the
implementation.  A wrapper implementation could certainly be provided
separate from either the slf4j or log4j implementations.
 
> 
> Thank you for this compromising proposal. As indicated previously, I'd
> be more than happy to scrap NLOG4J  as soon as the 1.2 branch offers a
> reasonable alternative implementation.

Do you consider "experimental" releases in parallel to the "official"
releases to be a "reasonable alternative"?
 
> Judging from earlier responses, I do not sense overwhelming enthusiasm
> for your proposal.  In the present situation, it  may be perhaps wiser
> to let  a strong  consensus emerge rather  than agree on  a compromise
> solution no one is really happy with.

I'm all for reaching a consensus that makes sense.
 
-Mark


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to