Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: neutral (asf.osuosl.org: 82.138.226.220 is neither permitted nor
 denied by domain of t.p.ellison@gmail.com)
Message-ID: <447C50D2.9090009@gmail.com>
Date: Tue, 30 May 2006 15:04:02 +0100
From: Tim Ellison <t.p.ellison@gmail.com>
User-Agent: Thunderbird 1.5.0.2 (Windows/20060308)
MIME-Version: 1.0
To: harmony-dev@incubator.apache.org
Subject: Re: [classlib] JNDI provider's dependency on logging
References: <E124AAE027DA384D8B919F93E4D8C70801F40493@mssmsx402nb>
 <447C40CB.5060002@pobox.com>
In-Reply-To: <447C40CB.5060002@pobox.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

I can guarantee best performance and no yammering by removing the
logging code ;-)

Seriously, VMs know exactly which methods are being executed and their
arguments, if we need trace or debug we can get lots of information from
there.  The logging statements are the equivalent of printf's in the
code to see what is happening.

Regards,
Tim

Geir Magnusson Jr wrote:
> I don't mind the dependency as much as I worry about the performance and
> the idea that our classlibraries might yammer out to stdout or logging
> infrastructure to the surprise of the users....
> 
> geir
> 
> 
> Zakharov, Vasily M wrote:
>> Tim,
>>
>> I see your point of removing extra inter-dependencies between the
>> modules,
>> however I'm surprized by the idea of removing dependencies on Logging.
>>
>> Logging is a package specifically created to organize and structurize
>> logging and debugging output, and I see using it as a good side of
>> implementation
>> of any component, as it provides the capability of having rich and
>> detailed
>> debugging output that can be switched on and off using standard means.
>>
>> Removing logging calls from Harmony components will make those
>> components
>> harder to debug and develop in future. Is it what we want?
>>
>> Vasily Zakharov
>> Intel Middleware Products Division
>>
>>
>> -----Original Message-----
>> From: Tim Ellison [mailto:t.p.ellison@gmail.com] Sent: Tuesday, May
>> 30, 2006 3:51 PM
>> To: harmony-dev
>> Subject: [classlib] JNDI provider's dependency on logging
>>
>> I've just imported the HARMONY-256 contribution of a DNS provider for
>> JNDI into our repository.  That provider introduces a new dependency
>> between JNDI and LOGGING that we didn't have before.
>>
>> IIRC we agreed that we would not scatter logging calls throughout our
>> implementation code, so unless I hear an objection I'll start to unpick
>> that dependency and make JNDI independent of LOGGING.
>>
>> Regards,
>> Tim
>>
> 
> ---------------------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
> 
> 

-- 

Tim Ellison (t.p.ellison@gmail.com)
IBM Java technology centre, UK.

---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org