<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I agree, it might be helpful to also have a simple code example
too. As for the rest of the requirements, they look good to me.<br>
<br>
On 12/01/12 15:10, Christian Kaltepoth wrote:
<blockquote
cite="mid:CAEXeC6xnqwy7-UHeMFK1zDxF3PCGkEqdZd5QTfCnzxbuv7dhvA@mail.gmail.com"
type="cite">Hi,
<div><br>
</div>
<div>with "type safe logging" you are referring to typed loggers
like implemented in Solder, right? In this case you could
perhaps add a sentence what type safe logging actually is. I
don't think that everybody knows that.</div>
<div><br>
</div>
<div>Christian</div>
<div><br>
</div>
<div><br>
<div class="gmail_quote">2012/1/12 Ken Finnigan <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:ken@kenfinnigan.me">ken@kenfinnigan.me</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
As per today's Seam meeting, below is a draft of an email
I'll send to the DeltaSpike mailing list to re ignite the
logging discussion, as it is on hold at present.<br>
<br>
Please provide feedback on content and language used, as I
want this to get the discussion off on the right foot.<br>
<br>
Ken<br>
<br>
=============================<br>
All,<br>
<br>
As we approach a 0.1 release of DeltaSpike, congratulations
to everyone on the good work so far, I feel it's a good time
to begin discussing how we want to handle logging within
DeltaSpike. I certainly don't expect this discussion to
result in code for 0.1, but the earlier we begin this
discussion, then it increases the likelihood of it being
ready for 0.2<br>
<br>
Having been heavily involved in the logging work for Solder,
I know the pain that can be experienced in not getting it
right, and also how long it can take to get right.<br>
<br>
I see that there are several goals that we want for logging
in DeltaSpike:<br>
<ol>
<li>Make it simple for both extension writers and end
users. If it's too difficult to implement, use or even
get right, then we'll frustrate and alienate developers.</li>
<li>It must perform. We don't want to introduce large
overhead to logging.</li>
<li>There should be an option to allow/provide type safe
logging.</li>
<li>An end user should be able to have DeltaSpike log
against whichever logging library they want to utilize
in their application. We can certainly support a
specific framework as a default, but it's important to
allow a developer to have the same control over how
DeltaSpike is logged as their own application.</li>
</ol>
<p>Thoughts?</p>
<p>Regards</p>
<span class="HOEnZb"><font color="#888888">
<p>Ken Finnigan</p>
<p>============================</p>
<p><br>
</p>
</font></span><br>
_______________________________________________<br>
seam-dev mailing list<br>
<a moz-do-not-send="true"
href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a><br>
<a moz-do-not-send="true"
href="https://lists.jboss.org/mailman/listinfo/seam-dev"
target="_blank">https://lists.jboss.org/mailman/listinfo/seam-dev</a><br>
<br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
Christian Kaltepoth<br>
Blog: <a moz-do-not-send="true"
href="http://chkal.blogspot.com/">http://chkal.blogspot.com/</a><br>
Twitter: <a moz-do-not-send="true"
href="http://twitter.com/chkal">http://twitter.com/chkal</a><br>
<br>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
seam-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:seam-dev@lists.jboss.org">seam-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/seam-dev">https://lists.jboss.org/mailman/listinfo/seam-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>