<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://mylnikovsergey.ulitzer.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Mylnikov Sergey</title>
 <link>http://mylnikovsergey.ulitzer.com/</link>
 <description>Latest News from Mylnikov Sergey</description>
 <language>en</language>
 <copyright>Copyright 2012 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Thu, 17 May 2012 19:52:08 EDT</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Asynchronous Logging Using Spring</title>
 <link>http://mylnikovsergey.ulitzer.com/node/2123093</link>
 <description>Each application developer faces the problem of logging usage information. On the one hand, the more logging that’s done the easier it is to detect and locate the source of problems. On the other hand, large volume logging might impair an application’s performance.
This problem is typically solved by defining various log levels dependent on a program’s maturity. For example, a program in developmental stages would have a higher logging requirements; logging requirements would be relatively lower in the production phase. If an application requires a lot of logging for audit purposes, then special measures are required to protect performance.
This article provides a possible solution for this problem by using Spring asynchronous support.
Logging is used extensively to help find problems within applications. A developer who finds a problem can investigate it by enabling debug logging. He may then reproduce the problem, or create additional logging if needed. Programmers usually require extensive logging to locate problems.&lt;p&gt;&lt;a href=&quot;http://mylnikovsergey.ulitzer.com/node/2123093&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 12 Jan 2012 10:45:00 EST</pubDate>
 <guid isPermaLink="true">http://mylnikovsergey.ulitzer.com/node/2123093</guid>
 <comments>http://mylnikovsergey.ulitzer.com/node/2123093#feedback</comments>
</item>
</channel>
</rss>

