From general-return-1964-apmail-logging-general-archive=logging.apache.org@logging.apache.org Tue Aug 7 05:37:56 2012 Return-Path: X-Original-To: apmail-logging-general-archive@www.apache.org Delivered-To: apmail-logging-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4BC299FBD for ; Tue, 7 Aug 2012 05:37:56 +0000 (UTC) Received: (qmail 11401 invoked by uid 500); 7 Aug 2012 05:37:56 -0000 Delivered-To: apmail-logging-general-archive@logging.apache.org Received: (qmail 11211 invoked by uid 500); 7 Aug 2012 05:37:53 -0000 Mailing-List: contact general-help@logging.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: "Logging General" List-Id: Delivered-To: mailing list general@logging.apache.org Received: (qmail 11187 invoked by uid 99); 7 Aug 2012 05:37:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Aug 2012 05:37:52 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of grobmeier@gmail.com designates 209.85.215.47 as permitted sender) Received: from [209.85.215.47] (HELO mail-lpp01m010-f47.google.com) (209.85.215.47) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Aug 2012 05:37:46 +0000 Received: by lagv3 with SMTP id v3so1633669lag.34 for ; Mon, 06 Aug 2012 22:37:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=wzvBNK4sWip9BBkAMFXdL6hIKbsJz9uxuR3npuyODnU=; b=GK8vXiLNpR0KhB5ghsGmxUdCXgVGcu5pBo7o8CmUdZvwTcIbV3rmYFWSVA/vmdW+Os 1jyMFoq8S3RVkJBbsb72xuFl+YFyf2/S1suddWD3qs2QD7kmaThxeuPnoXwH+4c3Q6Yo QuO4lep4SexwOSwstdfh/ulEN7fVcfguxom5uGNUhtiKKAyzeWJ4vCmrlXdSjoz3qjY3 u0K/GCzlXxZ3Oe5ADgUm2SgedHusglQmuSzVAq9JZtm+Guo04GzNZj5x3U524aFRxHW3 6u981Tb7hp60IKJEpfaf/+DnGqAjj8iAepIpvaM1waa3Ew2aW1Kev8TNutvNolzhKrBD epyA== Received: by 10.112.104.104 with SMTP id gd8mr5744978lbb.0.1344317846504; Mon, 06 Aug 2012 22:37:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.25.166 with HTTP; Mon, 6 Aug 2012 22:37:06 -0700 (PDT) In-Reply-To: References: From: Christian Grobmeier Date: Tue, 7 Aug 2012 07:37:06 +0200 Message-ID: Subject: ApacheCon Talk proposal To: Logging General Content-Type: text/plain; charset=UTF-8 hello all, I want to share the proposal I just submitted. I am really open for changes and improvements, just let me know. It is possible to edit the proposal afterwards. Cheers Christian World Of Logging Abstract: Apache Logging is one of the oldest projects from the Apache software foundation. It contains log4j, one of the most well-known libraries in the Java world. But there is more: the success of log4j has inspired many other developers. In this talk you will learn about the whole world of Apache logging: what is happening right now and why are the people so excited about their latest releases? Detail Abstract: Apache Logging is one of the oldest projects from the Apache software foundation. It contains log4j, one of the most well-known libraries in the Java world. But there is more: the success of log4j has inspired many other developers. A few of them has brought their work to the Apache Logging project also. In this talk you will learn about the whole world of Apache logging. In this talk we will discuss not only the overall state of the project and how it managed to return from a near death experience to an active community. We will also look at many of the subprojects, including the brand-new log4j 2, log4php, log4net, chainsaw or companions. In the case of log4j you'll learn that the only answer on the Logging War can be "peace" (as to every war). We'll look at the new plugin system and other great things, which comes with it. But there will be short introductions into log4php and log4net also; how do they differ from their Java brother? For example, PHP is a scripting language. How do we ensure quality and, heck, can that work out? Some of you might know about Chainsaw - the old, old logfile viewer. Or not? We will shortly look at how it works and what we can expect from it in the future with log4j 2.0 arriving. The whole talk will not be too technical. -- http://www.grobmeier.de https://www.timeandbill.de