Return-Path: 
 <dev-return-37139-apmail-geronimo-dev-archive=geronimo.apache.org@geronimo.apache.org>
Delivered-To: apmail-geronimo-dev-archive@www.apache.org
Received: (qmail 2102 invoked from network); 28 Aug 2006 07:32:32 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 28 Aug 2006 07:32:32 -0000
Received: (qmail 83360 invoked by uid 500); 28 Aug 2006 07:32:30 -0000
Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org
Received: (qmail 83324 invoked by uid 500); 28 Aug 2006 07:32:30 -0000
Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@geronimo.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@geronimo.apache.org>
List-Post: <mailto:dev@geronimo.apache.org>
Reply-To: dev@geronimo.apache.org
List-Id: <dev.geronimo.apache.org>
Delivered-To: mailing list dev@geronimo.apache.org
Received: (qmail 83313 invoked by uid 99); 28 Aug 2006 07:32:29 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Aug 2006 00:32:29 -0700
X-ASF-Spam-Status: No, hits=0.5 required=10.0
	tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of gnodet@gmail.com designates
 64.233.182.186 as permitted sender)
Received: from [64.233.182.186] (HELO nf-out-0910.google.com) (64.233.182.186)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 28 Aug 2006 00:32:29 -0700
Received: by nf-out-0910.google.com with SMTP id n29so1323081nfc
        for <dev@geronimo.apache.org>; Mon, 28 Aug 2006 00:32:07 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=Q1+oWSUtA90zFpC3SYt4v+fcT4X/vWBZucM4S+KM/wdpUH2lMhaLiRP7WDwZXNsOEukaFwuquif1d5qu7UeN1IxUD58yGIMGydXuOSEfWvD1+hgNgDS+xwm5KFKIw7pKd8fvDEG3NyHCPMVExvnfTkm2XIseUWd9bbuPJ5pKFKo=
Received: by 10.48.242.19 with SMTP id p19mr8687184nfh;
        Mon, 28 Aug 2006 00:32:07 -0700 (PDT)
Received: by 10.49.85.1 with HTTP; Mon, 28 Aug 2006 00:32:07 -0700 (PDT)
Message-ID: <b23ecedc0608280032s3a57f476g65df483fa81f3d36@mail.gmail.com>
Date: Mon, 28 Aug 2006 09:32:07 +0200
From: "Guillaume Nodet" <gnodet@gmail.com>
To: dev@geronimo.apache.org
Subject: Re: Why ClockDaemon instead of java.util.Timer?
In-Reply-To: <DF01674A-56A9-4843-8500-300AD2D0291E@planet57.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_50885_29050836.1156750327711"
References: <DF01674A-56A9-4843-8500-300AD2D0291E@planet57.com>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

------=_Part_50885_29050836.1156750327711
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I think we should switch to backport-util-concurrent instead of concurrent.
This will allow for easier switch to full JDK 5 later (and this is the
library used
by retrotranslator, btw).

On 8/28/06, Jason Dillon <jason@planet57.com> wrote:
>
> Does not look like ClockDaemon is going to ever make it into
> java.util.concurrent (or the backport).  I've also found several sources
> online that suggest that "Doug Lea says that it replaces its ClockDaemon
> class.", though I have not actually found anywhere that Doug actually says
> that.
> It also looks like ClockDaemon was added way back before there was
> java.util.Timer in the JDK... and I'm guessing that since they did not
> bring it into java.util.concurrent that it is probably recommended to just
> use java.util.Timer.
> --jason
>



-- 
Cheers,
Guillaume Nodet

------=_Part_50885_29050836.1156750327711
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I think we should switch to backport-util-concurrent instead of concurrent.<br>This will allow for easier switch to full JDK 5 later (and this is the library used<br>by retrotranslator, btw).<br><br><div><span class="gmail_quote">
On 8/28/06, <b class="gmail_sendername">Jason Dillon</b> &lt;<a href="mailto:jason@planet57.com">jason@planet57.com</a>&gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div style="">Does not look like ClockDaemon is going to ever make it into java.util.concurrent (or the backport).&nbsp; I've also found several sources online that suggest that &quot;<font face="Arial">Doug Lea says that it replaces its ClockDaemon class.&quot;, though I have not actually found anywhere that Doug actually says that.
</font><div><font face="Arial"><br></font></div><div><font face="Arial">It also looks like ClockDaemon was added way back before there was java.util.Timer in the JDK... and I'm guessing that since they did not bring it into 
java.util.concurrent that it is probably recommended to just use java.util.Timer.</font><div><font face="Arial"><br></font></div><div><font face="Arial">--jason</font></div></div></div>
</div></blockquote></div><br><br clear="all"><br>-- <br>Cheers,<br>Guillaume Nodet

------=_Part_50885_29050836.1156750327711--